Package: lockfile-progs
Version: 0.1.10

the program lockfile-create automatically adds the .lock extension to the 
supplied filename. but it does not talk about that in its manpage.

the C function lockfile_create does NOT add a .lock extension.

(the program dotlockfile does NOT add .lock extension and even explicitly sais 
this in its manpage.)


I had bad experiences which made me find this bug:

i wrote a C program which locks a directory using a lockfile. in order to be 
consistent i wanted to use some library and found liblockfile.

then i wrote a shellscript which should interact with the C-program. it must 
also lock the directory with the same lockfile of course. so i found 
lockfile-progs and expected it to have the same behaviour as the c function 
it uses. and bang there was the problem:

lockfile_create("foobar",10,0); -> creates "foobar"
lockfile-create foobar -> creates "foobar.lock"


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to