[EMAIL PROTECTED] ("Christian Jung") writes:
> Error: /proc must be mounted
> ...
> The System is a debian. Kernel 2.6.3 + vserver patch-2.6.3-vs0.09.diff
Since you are using the experimental kernel patch, you can try the alpha
branch of util-vserver:
http://www.linux-vserver.org/index.php?
On Fri, 2004-03-19 at 23:55, Christian Jung wrote:
> I did not find anything usefull in the groups. There was something
> mentioned
> that the proc filesystem is hidden for security reasons and that this
> can be
> changed with a tool. I did not really understand this, sorry.
>
As the procfs expo
Hi,
I upgraded my system and now i am in the following
situation:
All the vservers work fine beside the fact that on
every
vserver enter the systems tells me:
Error: /proc must be mounted To mount
/proc at boot you need an /etc/fstab line
like: /proc /proc
proc defaults In
On Fri, Mar 19, 2004 at 08:45:48PM +0100, Ivo De Decker wrote:
> On Fri, Mar 19, 2004 at 07:48:35PM +0100, Herbert Poetzl wrote:
> > On Fri, Mar 19, 2004 at 04:19:03PM +0100, Ivo De Decker wrote:
> > > Hello,
> > >
> > > The current vserver patch (1.26) doesn't limit the use
> > > of ipv6 address
On Fri, Mar 19, 2004 at 07:48:35PM +0100, Herbert Poetzl wrote:
> On Fri, Mar 19, 2004 at 04:19:03PM +0100, Ivo De Decker wrote:
> > Hello,
> >
> > The current vserver patch (1.26) doesn't limit the use of ipv6 addresses in
> > vservers. The attached patch should disable ipv6 inside vservers, maki
On Fri, Mar 19, 2004 at 04:19:03PM +0100, Ivo De Decker wrote:
> Hello,
>
> The current vserver patch (1.26) doesn't limit the use of ipv6 addresses in
> vservers. The attached patch should disable ipv6 inside vservers, making it
> possible to enable ipv6 on the main server, without problems cause
But isn't 127.0.0.1 mapped to the vserver IP anyway:
# vserver grisha enter
ipv4root is now 192.168.1.187
New security context is 10187
[EMAIL PROTECTED]:grisha /]telnet 127.0.0.1 25
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
220 grisha.ispol.com ESMTP Sendmail 8.12.10
Hello,
The current vserver patch (1.26) doesn't limit the use of ipv6 addresses in
vservers. The attached patch should disable ipv6 inside vservers, making it
possible to enable ipv6 on the main server, without problems caused by users
inside vservers.
Comments? Ideas?
Greetings,
Ivo De Decker
[EMAIL PROTECTED] (Herbert Poetzl) writes:
> vproc was an experimental tool, and should by now be replaced by
> setattr (from util-vserver), enrico, please confirm ...
True for alpha branch, false for stable...
Enrico
___
Vserver mailing list
[EMAIL
Am Donnerstag, 18. März 2004 16:29 schrieb Enrico Scholz:
> [EMAIL PROTECTED] (Thomas Guettler) writes:
> > If you use "--cap CAP_NET_RAW" with chcontext chroot is not possible.
>
> I know about miscompilations with SuSE 9 (gcc 3.3.1). Can you try the
> '-O0' flag and see if problem still exists?
Am Mittwoch, 17. März 2004 11:29 schrieb Herbert Poetzl:
> On Wed, Mar 17, 2004 at 10:57:27AM +0100, Thomas Guettler wrote:
[cut]
> vproc /proc/[a-z]* should do nicely (but is not secure)
>
> > vproc does return 0 if failed. Should be easy to fix.
>
> vproc was an experimental tool, and should by
11 matches
Mail list logo