Re: [documancer] Failed to lock the lock file

[Vaclav S. <vac...@ma...>]

Hi,

[I'm CC'ing this to wx-users because it's a wxWindows question and=20
hopefully somebody will be able to give better answer than me]

arn...@we... wrote:
> I managed to compile
> Python/wxPython/mozilla/wxMozilla/swish-e/documancer on a SUSE
> Athlon based machine in our PC-Pool.
> Everything looks pretty fine, however, when trying to start
> documancer I get:
>   "Failed to lock the lock file
>   '/home/baecker/.documancer/documancer-baecker'
>   (error 37: Keine Sperren verfuegbar)
> ((I think this error 37 should roughly translate to "no locks
> available" - hmm, internationalization can be a pain ;-)).

And does it continue running after that? Failure to make the lock is=20
not fatal for Documancer (you only risk some damage if running two=20
instances of the app at the same time by the same user).=20

> I have no idea why this happens (the .documancer directory
> is created and also writable by the user).
> If it is of any importance here: the home-directories
> are NFS mounted and the access can be pretty slow sometimes.

Yes, it is, locking may not work over NFS. First thing to check is if=20
your wxWindows' copy setup.h has HAVE_FCNTL defined. If not, then it=20
won't work (see man flock). The same (Linux) manpage says that=20
fcntl() does work over NFS, "given a sufficiently recent version of=20
Linux and a server which supports locking."

I could create the lock file in $TMPDIR instead of in $HOME, but I=20
don't what what the current best practise is, security-wise.

Regards,
Vaclav

=2D-=20
PGP key: 0x465264C9, available from http://pgp.mit.edu/