licq won't start with configuration directory on nfs share

[nitram29@…]

Hello, when the .licq configuration directory is located on a nfs share I get this error message:

[ERR] Licq: Already running at pid 1

[root_42]

I cannot reproduce this behavior, my .licq also lies on a NFS share. Can you please give the options given in /etc/exports for this NFS share? Also please tell us the access rights of the files in .licq.

[nitram29]

Replying to root_42:

I cannot reproduce this behavior, my .licq also lies on a NFS share. Can you please give the options given in /etc/exports for this NFS share? Also please tell us the access rights of the files in .licq.

mount shows me the following options for the mounted nfs share:

rw,nosuid,nodev,hard,intr,rsize=8192,wsize=8192,rsize=8192,wsize=8192

All of the files in .licq/ have at least a 600, directories 700 pattern. But the very same files with the same rights work when copied on a local drive.

[erijo]

Make sure your nfs server supports locking (see nfs(5) nolock option). If it does, perhaps a restart of the nfs server would help.

[nitram29]

I have no real access to that nfs server. licq 1.3.2 was working with .licq on the nfs share.

[erijo]

Licq 1.3.4 has a new way of determining if another instance of Licq is already running. It now uses fcntl (2) and F_SETLK to acquire a write lock that's held until the process is killed. This is an improvement over the previous method and it should work on nfs as well.

Please contact your administrator and ask if he/she can configure the server to support locking. If this isn't possible, we could add a flag to Licq that would allow it to start even if it's unable to acquire the lock.