Package: liblockfile-bin Version: 1.11-1 Severity: normal File: /usr/bin/dotlockfile
Dear Maintainer, I tried to use lockfile_create on an sshfs mountpoint. When it did not work I ran some tests with the commandline utility dotlockfile. While the lockfile_create option exists with error code 4, the commandline utility exits with error code 2 (permission denied), unless the -o allow_other option is provided to sshfs, in which case the error code is 4 (and one has to wait around a minute or so for the program to exit). I have checked that the mountpoint is readable and writable by the user starting the command. I have tried giving various options to sshfs, to no avail, the error code is either 2 (imemdiately) or 4 (after some time). Long story short, here are the steps to reproduce: $mkdir /tmp/dir1 $mkdir /tmp/dir2 $sshfs $(whoami)@127.0.0.1:/tmp/dir1 /tmp/dir2 $dotlockfile /tmp/dir1/test1.lock # Direct access, this works $dotlockfile /tmp/dir2/test2.lock # Through SSHFS, does not work dotlockfile: /tmp/dir2/test2.lock: permission denied $touch /tmp/dir2/test2.lock # Checking our write access $ls /tmp/dir1 test1.lock test2.lock Thank you for your work so far, and thanks in advance for any help you may provide with this bug. -- System Information: Debian Release: 8.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages liblockfile-bin depends on: ii libc6 2.19-18+deb8u6 liblockfile-bin recommends no packages. liblockfile-bin suggests no packages. -- no debconf information
