Re: [documancer] Failed to lock the lock file

--Boundary-02=_HQ/IAY32mk3thC+
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

Arnd Baecker wrote:
> if I am able to resolve
> this locally (which I have some doubts right now),
> the problem may in general occur for other users as well.

Yes, probably. I already modified Documancer to work even if locking=20
fails and I could move the lock file to $TMPDIR (which is almost=20
certainly not on NFS volume) after we fix wxSingleInstanceChecker to=20
not be vulterable to a DoS attack by another user if he can access=20
the lock file.

> BTW: wouldn't a normal file just serve the same purpose
> of saying "There is already a documancer instance running" ?
> (But presumably I am missing something ...)

There would be race condition related to writing and reading process=20
PID to/from the lock file.

Regards,
Vaclav

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

--Boundary-02=_HQ/IAY32mk3thC+
Content-Type: application/pgp-signature
Content-Description: signature

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

iD8DBQBAI/QHxDYa/UZSZMkRAvaGAJ9iOxnpxCvqX2Hj0mGckpo5D8cuuACgkl/h
Fw7wj5KrVjrBUnkOI/nAL1g=
=Pl9c
-----END PGP SIGNATURE-----

--Boundary-02=_HQ/IAY32mk3thC+--


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn