From: Herbert Poetzl (herbert_at_emcc.at)
Date: Thu 11 Jul 2002 - 09:00:46 BST
On Thu, Jul 11, 2002 at 10:37:01AM +0300, Jukka Laaksola wrote:
> Jacques Gelinas wrote:
> >
> > The other is NIS. The NIS server and client (ypbind) works correctly inside vservers,
> > but ypwhich fails to talk to ypbind.
>
> I have vserver 0.17 and ctx-10.
>
> I have in /etc/hosts on 10.10.10.41
> -----
> 10.10.10.41 vserver2 localhost
> 10.10.10.40 vserver1
> ---
> [root_at_vserver2 /]ypwhich
> ypwhich: Can't communicate with ypbind
> [root_at_vserver2 /]ypwhich localhost
> vserver1
> [root_at_vserver2 /]
>
> So I have for a work around changed /etc/init.d/ypbind startup script to
> use "ypwhich localhost" and it will found the NIS server.
>
> >
> > Anyone knows of other package needing special handling on the loopback ?
>
> I'm not sure if this is a real loopback problem or what.
> Portmap only in vservers works fine for me. But I need to run portmap
> also in the main server for NFS-server. This is need special tricking.
> If I start portmap normally in the main server then portmap in a vserver
> can't bind the udp address. Now I use in main server "chbind --ip
> 127.0.0.1 /etc/init.d/portmap start". Then I need to use rinetd for
> forwarding nfs-servers IP's (192.168.0.3) tcp port 111 to localhost port
> 111. I haven't found a solution for forwarding udp port also.
have you tried running portmap in two different
virtual hosts?
if this works, a simple chbind --ip <master-ip>
should do the trick ...
(like the v_sshd, v_httpd, etc ... scripts)
best,
Herbert