Samuel, Thanks for reply, I didn't get your reply because I am not hurd mailing list there for my late respons. Do I need to report a bug for getting this patched ? With kind regards, Bas van den Dikkenberg > Bas van den Dikkenberg, le Sat 01 Mar 2014 09:17:56 +0000, a écrit : > > My build of the package burp that I maintain, keeps failing during the test > failing with these error messages: > > > > 2014-02-25 20:53:14: burp[716] Could not get lock > > /<PKGBUILDDIR>/test/target/var/run/burp.server.pid: Not supported > > 2014-02-25 20:53:14: burp[716] Could not get lockfile. > > 2014-02-25 20:53:14: burp[716] Another process is probably running, > > 2014-02-25 20:53:14: burp[716] or you do not have permissions to write to > /<PKGBUILDDIR>/test/target/var/run/burp.server.pid. > > > > Is the pid system not support on hurd ? > > It is supported, otherwise very few applications would run :) > > The error is during locking the file. The code is doing lockf(fdlock, F_TLOCK, > 0), but the Hurd doesn't have lockf record locking yet, only whole file lock. > That being said, burp is actually locking the whole file, current position > being > 0 and length being 0. We can probably patch glibc in > sysdeps/mach/hurd/fcntl.c when whence is SEEK_CUR to read the current > position and test whether it is 0. > > Samuel
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]

