David Schmitt wrote:
It seems that /usr/sbin/vlimit dies when the path to the config directory contains a symlink:tom:/etc/vservers# ls -lad apt-cacher lrwxrwxrwx 1 root root 44 Aug 29 13:48 apt-cacher -> /var/lib/vservers/_infra/_config/apt-cacher/ tom:/etc/vservers# vserver apt-cacher start vlimit: fstat("/etc/vservers/apt-cacher/rlimits"): Permission denied [...] The same config works, when bind-mounting the config into place. /var/lib/vservers/_infra is on external storage which can be accessed by a standby server in case of a failure, therefore I also need the configon this volume.
The problem is not with the symlink at all, it's the fact that you put it inside a directory that's protected by the barrier, and as such it's supposed to be inaccessible from anything but xid 0 (and recently xid 1). vlimit just happens to be the first command the start sequence runs after creating and initially migrating into the context.
-- Daniel Hokka Zakrisson GPG id: 06723412 GPG fingerprint: A455 4DF3 990A 431F FECA 7947 6136 DDA2 0672 3412 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
