ben+python at benfinney.id.au
Sun Mar 29 01:37:00 CET 2009
aahz at pythoncraft.com (Aahz) writes:
> In article <87iqlwvemo.fsf at benfinney.id.au>,
> Ben Finney <bignose+hates-spam at benfinney.id.au> wrote:
> >In the case of the â€˜lockfileâ€™ library, Skip is aiming for a
> >cross-platform solution, with atomic behaviour; he has implemented
> >lock acquisition with a â€˜linkâ€™ operation on Unix, and a
> >â€˜mkdirâ€™ operation on Windows.
> >But both of those, of course, create a new file. What I want is to
> >lock an existing file. Is â€˜lockfâ€™ particularly prone to
> >cross-platform troubles on Unix variants? (Since the â€œbecome a
> >daemonâ€� pattern makes no sense on anything but Unix, I'm only
> >concerned with PID file behaviour that works on Unix.)
Hmm, looks like your client is messing up character encoding.
> IIUC, you must use something like Skip's trick to work correctly with
Okay. But is that something that needs to be accommodated with,
specifically, PID file handling? Why would a PID file ever need to be
on NFS storage instead of local?
\ “The cost of a thing is the amount of what I call life which is |
`\ required to be exchanged for it, immediately or in the long |
_o__) run.” —Henry David Thoreau |
More information about the Python-list