On Wed, Dec 30, 2009 at 01:36:03PM +1100, Fog_Watch wrote: > On Tue, 29 Dec 2009 16:23:10 +0100 > Herbert Poetzl <herbert@13thfloor.at> wrote: > > > good, then the next step is to try in a context but on > > the host filesystem, i.e. start autofs with: > > > > chcontext --xid 42 -- /etc/init.d/autofs start > > > > and check if that fails > I am not sure what is meant by "fail": I simply meant 'misbehave' i.e. do not work as without the context change ... > hostname ~ # chcontext --xid 32 -- ps aux | grep automount > hostname ~ # chcontext --xid 32 -- /etc/init.d/autofs start > * Starting automounter ... [ ok ] > hostname ~ # chcontext --xid 32 -- ps aux | grep automount > root 13062 0.0 0.0 4848 1048 ? Ssl 10:44 > 0:00 /usr/sbin/automount -p /var/run/autofs.pid > hostname ~ # chcontext --xid 32 -- /etc/init.d/autofs stop > * Stopping automounter ... [ ok ] > hostname ~ # chcontext --xid 32 -- ps aux | grep automount > hostname ~ # > That is not a failure. > hostname ~ # chcontext --xid 32 -- /etc/init.d/autofs start > * Starting automounter ... [ ok ] > hostname ~ # chcontext --xid 32 -- ps aux | grep automount > root 11179 0.0 0.0 5872 1048 ? Ssl 13:04 > 0:00 /usr/sbin/automount -p /var/run/autofs.pid > hostname ~ # chcontext --xid 32 -- ls /mnt/cdrom ; df | grep cdrom > Getting_Online.txt README.txt docs gentoo.efimg image.squashfs > isolinux livecd snapshots > /dev/sr0 717098 717098 0 > 100% /mnt/removables/cdrom > hostname ~ # chcontext --xid 32 -- df | grep cdrom > df: `/proc/fs/nfsd': No such file or directory > df: `/vservers/as': No such file or directory > df: `/vservers/hf': No such file or directory > df: `/vservers/voip': No such file or directory > df: `/vservers/fw': No such file or directory > df: `/vservers/template': No such file or directory > df: `/vservers/voiptest': No such file or directory > df: `/vservers/as/home': No such file or directory > hostname ~ # > I don't think that is a failure either because /mnt/cdrom appears > to auto-mount and auto-umount inside the context. looks good to me, so I'd say, the Linux-VServer context is not your problem, but it might be related to the way util-vserver sets up the namespaces ... just to narrow it down, try to disable namespaces for your guest and see if the issue remains ... > Is an strace still needed? I guess it wouldn't hurt to get those, also keep the discussion on the list, as others, like Daniel might join the discussion ... > I have confirmed the problematic behaviour with > # automount -V > Linux automount version 4.1.3 > > # automount -V | grep version > Linux automount version 5.0.4 > > As well as the original > # automount -V | grep version > Linux automount version 5.0.3 > > Regards and thanks for your time. > > Fog_Watch > > PS > I've sent this directly as the others on the list might be > getting bored with this autofs chatter. no need, that's what the list is for ... best, Herbert > -- > Lose wait. Get Gentoo.