Hello
I'm running a debian Linux version 2.6.12.2-vs2.0-rc5. I've compiled
util-vserver 0.30 from linux-vserver.org but i got the following error when
i when to start a vserver :
Can't set the ipv4 root (Invalid argument)
I didn't have this problem with previous version from kernel 2.4.25 to
You'll need to use NGN to do that. After extensive testing and
experimentation, I concluded that the GNU C libraries had it
hardcoded
in too many places that localhost == 127.0.0.1.
What ist NGN and where can I find it. (can't find on google,...)
This means turning on the formidable disable
Hi!
Here is a little problem+solution report for vserver 1.9.5,
I am running linux 2.6.11.7 with vserver patch-2.6.11.6-vs1.9.5.12.diff.gz.
The problem: attempt to read /proc/net/route inside a vserver results
in program termination with a SIGSEGV. This is accompanied by the
following Oops:
On 2005.07.07 13:51:57 +0200, [EMAIL PROTECTED] wrote:
Hello,
i'm working on a netfilter-configuration for the host-server ...
Can i protect one vserver against another?
I testet the following:
{...}
# Block everything between 2 vserver
iptables -A INPUT -d 192.168.0.155 -s
On Thu, Jul 07, 2005 at 11:52:46AM +0200, Tilo Kaltenecker wrote:
You'll need to use NGN to do that. After extensive testing and
experimentation, I concluded that the GNU C libraries had it
hardcoded
in too many places that localhost == 127.0.0.1.
What ist NGN and where can I find it.
On Thu, Jul 07, 2005 at 09:15:39AM +0200, Patrick Home wrote:
Hello
I'm running a debian Linux version 2.6.12.2-vs2.0-rc5. I've compiled
util-vserver 0.30 from linux-vserver.org but i got the following error when
i when to start a vserver :
Can't set the ipv4 root (Invalid argument)
On Thu, Jul 07, 2005 at 02:14:02PM +0200, Oliver Welter wrote:
Hi Oliver,
Can i protect one vserver against another?
I testet the following:
{...}
# Block everything between 2 vserver
iptables -A INPUT -d 192.168.0.155 -s 192.168.0.157 -j DROP
iptables -A INPUT -d 192.168.0.157 -s
Hi,
while digging in the util-vserver source code I found a problem with
the handling of comments in several files under /etc/vserver/*
(bcapabilities, ccapabilities, capabilites, flags). The code that
tests if a line is a comment looks for '^#$', not '^#.*$'.
The attatched patch fixes this.
Hi,
I've written a patch that adds some more documentation to the
vserver kernel config options. I hope it makes the effect of these
options a bit clearer for people.
CONFIG_VSERVER_HARDCPU stuff is taken from the wiki (and was the
reason I wrote this patch in the first place), and is thusly
On Thursday 07 July 2005 20:55, Christian Aichinger wrote:
Hi,
I've written a patch that adds some more documentation to the
vserver kernel config options. I hope it makes the effect of these
options a bit clearer for people.
CONFIG_VSERVER_HARDCPU stuff is taken from the wiki (and was the
10 matches
Mail list logo