Good spot, thanks: /var/lock is on /, not a symlink to /var/run.
These machines are provisioned from OVH.com templates. I have raised a support request with them to see if they are aware of this or are doing anything strange on purpose.
--
$ cat /proc/self/mountinfo | fgrep lock 27 20 0:19 / /run/lock rw,nosuid,nodev,noexec,relatime - tmpfs none rw,size=5120k
$ df -h /var/lock Filesystem Size Used Avail Use% Mounted on /dev/disk/by-uuid/56f53efc-[..] 20G 3.2G 15G 18% /
$ ls -ld /var/lock drwxrwxrwt 2 root root 4096 Nov 12 10:42 /var/lock
$ df -h /run/lock Filesystem Size Used Avail Use% Mounted on none 5.0M 0 5.0M 0% /run/lock
Good spot, thanks: /var/lock is on /, not a symlink to /var/run.
These machines are provisioned from OVH.com templates. I have raised a support request with them to see if they are aware of this or are doing anything strange on purpose.
--
$ cat /proc/self/ mountinfo | fgrep lock nodev,noexec, relatime - tmpfs none rw,size=5120k
27 20 0:19 / /run/lock rw,nosuid,
$ df -h /var/lock by-uuid/ 56f53efc- [..] 20G 3.2G 15G 18% /
Filesystem Size Used Avail Use% Mounted on
/dev/disk/
$ ls -ld /var/lock
drwxrwxrwt 2 root root 4096 Nov 12 10:42 /var/lock
$ df -h /run/lock
Filesystem Size Used Avail Use% Mounted on
none 5.0M 0 5.0M 0% /run/lock