When one process is holding an exclusive lock on a file, and other
processes are waiting for the lock to be released, the contents of
/proc/locks look like this:
$ cat /proc/locks
1: FLOCK ADVISORY WRITE 431143 00:0f:6325223 0 EOF
1: -> FLOCK ADVISORY WRITE 405209 00:0f:6325223 0 EOF
1: -> FLOCK ADVISORY WRITE 399578 00:0f:6325223 0 EOF
1: -> FLOCK ADVISORY WRITE 434120 00:0f:6325223 0 EOF
2: FLOCK ADVISORY WRITE 359765 08:04:28180839 0 EOF
3: FLOCK ADVISORY WRITE 359765 08:04:28180837 0 EOF
4: POSIX ADVISORY WRITE 434729 08:04:8653261 0 EOF
4: -> POSIX ADVISORY WRITE 434737 08:04:8653261 0 EOF
5: FLOCK ADVISORY WRITE 359765 08:04:28180836 0 EOF
6: ...
If I try to run `lslocks`, it fails to parse the "->" lines and exits
with an error message:
lslocks: failed to parse pid: 'WRITE'
Can be reproduced by:
touch foo & flock foo -c "sleep 100" & flock foo -c "sleep 100" &
touch foo & lckdo -w foo sleep 100 & lckdo -w foo sleep 100 &
--
Mantas Mikulėnas <grawity@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
