[Vserver] Abnormal NFS behaviour

2007-06-27 Thread Jim Wight
I have upgraded a host and transferred its services into a guest; both run CentOS 5. Two other (Fedora Core 4) guests remain unchanged. Since the change, NFS mounting fails to work in any of the guests. The new one uses ccapabilities with SECURE_MOUNT, SECURE_REMOUNT and BINARY_MOUNT, while the

Re: [Vserver] Abnormal NFS behaviour

2007-06-27 Thread Jim Wight
On Wed, 2007-06-27 at 10:44 +0100, Ben Green wrote: On Wed, 27 Jun 2007 10:02:56 +0100, Jim Wight [EMAIL PROTECTED] wrote: I have upgraded a host and transferred its services into a guest; both run CentOS 5. Two other (Fedora Core 4) guests remain unchanged. Since the change, NFS mounting

Re: [Vserver] Abnormal NFS behaviour

2007-06-27 Thread Jim Wight
On Wed, 2007-06-27 at 12:39 +0100, Ben Green wrote: On Wed, 27 Jun 2007 12:10:38 +0100, Jim Wight [EMAIL PROTECTED] wrote: No, because my aim is not to run a server. I simply want the guests to be able to mount NFS filesystems from other hosts elsewhere on the nework. I have guests

Re: [Vserver] Abnormal NFS behaviour

2007-06-27 Thread Jim Wight
Not really sure if thats what you need, but a kind soul on the list once told me to use fstab.remote to mount remote nfs volumes I haven't mentioned that I'm using the automounter (autofs) to do the mounts, so unfortunately that doesn't help. Jim

Re: [Vserver] NFS mounts in guests [was: how to set capabilities in Debian]

2006-09-30 Thread Jim Wight
On Sat, 2006-09-30 at 13:23 +0200, Daniel Hokka Zakrisson wrote: Could you try applying http://people.linux-vserver.org/~dhozac/p/k/delta-nfs-fix01.diff to your kernel and see if that changes anything? This seems to have fixed NFS mounting from guests with binary_mount and secure_mount for

Re: [Vserver] how to set capabilities in Debian

2006-09-26 Thread Jim Wight
On Sat, 2006-09-23 at 18:40 +0200, Herbert Poetzl wrote: c) why would you want to add CAP_SYS_ADMIN to a guest? Taking 'you' in the sense of 'anyone', I would say for NFS. I don't want to hijack this thread, so can I refer you to one started by Wilhelm Meier on 13th Sep entitled 'How do I

Re: [Vserver] Host and guest compatability

2006-08-15 Thread Jim Wight
On Tue, 2006-08-15 at 02:33 +0200, Daniel Hokka Zakrisson wrote: Jim Wight wrote: My setup is 2.6.14.3-vs2.0.1 with 0.30.210. The vserver was created by dumping an installation on hardware and restoring it to /vservers/fc5 and then: One of my FC4 hosts is using 2.6.17-1.2142_FC4

Re: [Vserver] Host and guest compatability

2006-08-15 Thread Jim Wight
On Tue, 2006-08-15 at 02:33 +0200, Daniel Hokka Zakrisson wrote: Jim Wight wrote: My setup is 2.6.14.3-vs2.0.1 with 0.30.210. The vserver was created by dumping an installation on hardware and restoring it to /vservers/fc5 and then: One of my FC4 hosts is using 2.6.17-1.2142_FC4

Re: [Vserver] Host and guest compatability

2006-08-12 Thread Jim Wight
On Sat, 2006-08-12 at 16:39 +0200, Herbert Poetzl wrote: On Tue, Aug 08, 2006 at 08:46:04PM +0100, Jim Wight wrote: To what extent do the host and the guest have to be compatible? I'm getting this when trying to start a Fedora Core 5 guest on an FC4 host: # vserver fc5 start /usr

Re: [Vserver] Host and guest compatability

2006-08-09 Thread Jim Wight
On Wed, 2006-08-09 at 08:17 +0200, Guenther Fuchs wrote: on Tuesday, August 8, 2006 at 9:46:04 PM there was posted: JW To what extent do the host and the guest have to be compatible? Only to the kernel, no more, none else. That's what I thought. JW # vserver fc5 start JW

Re: [Vserver] Host and guest compatability

2006-08-09 Thread Jim Wight
On Wed, 2006-08-09 at 08:50 -0500, Michael S. Zick wrote: Since the chroot command does not change the context (or namespace) then it must be the act of trying to run in a different context that breaks something. My guess, the dynamic library handling. Try executing /lib/libc.so.6 in the

Re: [Vserver] Host and guest compatability

2006-08-09 Thread Jim Wight
On Wed, 2006-08-09 at 09:58 -0500, Michael S. Zick wrote: On Wed August 9 2006 09:30, Jim Wight wrote: On Wed, 2006-08-09 at 08:50 -0500, Michael S. Zick wrote: Since the chroot command does not change the context (or namespace) then it must be the act of trying to run in a different

[Vserver] Host and guest compatability

2006-08-08 Thread Jim Wight
To what extent do the host and the guest have to be compatible? I'm getting this when trying to start a Fedora Core 5 guest on an FC4 host: # vserver fc5 start /usr/bin/env: /lib/libc.so.6: version `GLIBC_2.4' not found (required by /usr/bin/env) An error occured while executing the

[Vserver] nodev with secondary interfaces

2006-07-13 Thread Jim Wight
The Great Flower Page says nodev can be used to assign primary interfaces which are created by the host or another vserver.. Are secondary interfaces to be avoided? After returning to the documentation I realised I had unwittingly used nodev with a secondary. I haven't noticed any ill effects in

RE: [Vserver] unmount nfs with vserver

2005-10-20 Thread Jim Wight
Ok my plan is to be able to mount/umount nfs disk from inside the guest/vserver. I'm still getting a permission denied. #Now that I have the ccaps in place properly (i hope) cat /usr/local/etc/vservers/unixdev1/ccapabilities SECURE_MOUNT SECURE_REMOUNT BINARY_MOUNT I also want to get

Re: [Vserver] Unexpected behaviour with bind mounts

2005-10-10 Thread Jim Wight
On Fri, 2005-10-07 at 22:00 +0200, Guenther Fuchs wrote: Hi there, on Friday, October 7, 2005 at 16:12 on the list was posted: Shutting down system logger: [ OK ] Starting killall: [ OK ] umount: /tmp: not

Re: [Vserver] sshd and ptys

2005-10-06 Thread Jim Wight
have devpts mounted in the vserver, but not with those options. Now I see that the original FC4 fstab used them, but I created my own fstab and must have transferred the devpts line with defaults from a previous version, and then that's what I used for the vserver. Jim Jim Wight a écrit

[Vserver] sshd and ptys

2005-10-05 Thread Jim Wight
I'm returning to VServer after being away from it for over a year. One thing that worked previously and isn't working for me now is remotely logging in via ssh. I see the following in /var/log/messages: sshd[11932]: error: openpty: Permission denied sshd[11932]: error: session_pty_req: session 0