On Tue, Sep 26, 2006 at 11:50:57AM +0200, Wilhelm Meier wrote:
> Am Dienstag, 26. September 2006 11:10 schrieb 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 nfs-mount
> > inside a vserver?', and which has gone quiet without being resolved.
> Thank you for reactivating!
it was not forgot, it is on my todo list ...
unfortunately I have no test systems available
ATM to test an nfs setup, but I will try to
recreate the setup with a QEMU network shortly
> > I have never
> > been able to get NFS to work without using CAP_SYS_ADMIN, even after
> > upgrading to 18.104.22.168-vs2.0.2/0.30.210,
> Seems to be still impossible in dev-branch vs2.1.1 (BINARY_MOUNT
> should do the job but doesn't)
in general, the answers to the following questions
could be very helpful:
- what NFS version and tcp or udp?
- what is the actual error you get?
- tcpdump of the ongoing negotiation?
- logs on both, client and filer with the
appropriate sysctl debug options enabled
> > and was on the point of raising the matter when that thread
> > appeared. I too would like to know the circumstances under which NFS
> > mounting can be achieved without resorting to CAP_SYS_ADMIN.
> > Jim
Vserver mailing list
Received on Tue Sep 26 17:06:32 2006