Hi chuck
I couldn't reply you for all the question but I'am using a 2.6.22.19-vs2.3.0.34 hand patched (not gentoo) on a production server since 43 days and I haven't any problem with it. My old vservers are all working correctly without mmodifications since my host sshd is not listening on 127.0.0.1 interface and the new vserver with true 127.0.0.1 is working fine too.
If gentoo has not unmasked it that is because they don't have suffisant return of users about it.
Regards
Chuck has wrote :
> we finally have a need for a true 127.0.0.1 inside a vserver :(
>
> we are presently running 2.6.20-vs2.2.0-gentoo on this amd64 host with 100+
> virtual servers running.
>
> according to what i have been reading in this list, i have to upgrade to
> the 'gentoo unstable' 2.3.0.29 or .34 versions to enable true localhost. is
> there any workaround using our existing installation? this particular vserver
> cannot use a remapped localhost to the primary ip. it must be a private
> 127.0.0.1.
>
> 1. would this upgrade be compatible with existing vservers? i do not wish to
> update every one of them.
>
> 2. i am not very happy about putting unstable code on a production machine. is
> this code ready for production yet? if so why has gentoo not unmasked it?
>
>
Received on Mon May 26 18:45:33 2008