Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RE: The DB_File locking method is flawed #531

Closed
p5pRT opened this issue Sep 20, 1999 · 2 comments
Closed

RE: The DB_File locking method is flawed #531

p5pRT opened this issue Sep 20, 1999 · 2 comments

Comments

@p5pRT
Copy link

p5pRT commented Sep 20, 1999

Migrated from rt.perl.org#1378 (status was 'resolved')

Searchable as RT1378$

@p5pRT
Copy link
Author

p5pRT commented Sep 20, 1999

From Steve

I thought locking data files was always frowned upon. Some
OSes mutilate
files when locking them or something (I think it tends to set its size
to zero). Or at least I've heard that it's always better to use a
separate, zero-length files as a lock.

This is from the Berkeley DB documentation regarding the "fd" function​:

  This file descriptor may be safely used as an argument to the
  fcntl(2) and flock(2) locking functions. The file descriptor is
  not necessarily associated with any of the underlying files actually
  used by the access method.
 

Seems like several people here have done things with File​::Lock or
LockFile or whatever.

Like what?

Paul

@p5pRT
Copy link
Author

p5pRT commented Apr 22, 2003

@iabyn - Status changed from 'stalled' to 'resolved'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant