Package: znc
Version: 0.092-3
Severity: normal
ZNC uses an exclusive lock on a file handle that is open read-only. This
operation is not supported on NFSv4, as described here:
http://www.spinics.net/lists/linux-nfs/msg18594.html
This problem makes znc unusable on NFSv4-mounted home directories, resulting in
error message:
[ !! ]is already running on this config. ]
(since it can't lock the file, it assumes someone else did!)
Relevant output of "strace -e open,flock znc":
open("/home/users/thewanderer/.znc/configs/znc.conf", O_RDONLY) = 3
flock(3, LOCK_EX|LOCK_NB) = -1 EIO (Input/output error)
I see two solutions:
0) Implement proper error checking when locking the config file. EIO is not
equal to EWOULDBLOCK!
1) Use a writable file, like znc.conf.lock (config file path with ".lock"
suffix appended), for exclusive locks.
-- System Information:
Debian Release: 6.0.2
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-rc5-rkaw+ (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
