Re: [documancer] Failed to lock the lock file

Hi,

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

arnd.baecker-S0/[email protected] 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 
not fatal for Documancer (you only risk some damage if running two 
instances of the app at the same time by the same user). 

> 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 
your wxWindows' copy setup.h has HAVE_FCNTL defined. If not, then it 
won't work (see man flock). The same (Linux) manpage says that 
fcntl() does work over NFS, "given a sufficiently recent version of 
Linux and a server which supports locking."

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

Regards,
Vaclav

-- 
PGP key: 0x465264C9, available from http://pgp.mit.edu/

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAIhnLxDYa/UZSZMkRAne0AKCloqGvlrrLUTP6HeeJaKAzwCJ8ngCgpOOD
b4WkZljCiGyYrskAWvgWPH4=
=R6yx
-----END PGP SIGNATURE-----