At 12:49 Uhr +0200 16.08.2004, Herbert Poetzl wrote:
So, the net effect is: If you configure your vservers to use two ip's
(for example: one for localhost purposes, and a second for public
local host 'purposes' is a bad idea anyway,
because linux-vserver networking does some
stuff to replace
Hello Herbert and Enrico
There is a problem with UDP port forwarding from a host doing NAT into
vservers which have multiple ip adresses. Depending on the order how
the ip addresses are fed to chbind, the forwarding will work or
not. TCP port forwarding is not affected.
Steps to reproduce:
You
At 10:19 Uhr +0200 17.07.2004, Dariush Pietrzak wrote:
At 15:09 Uhr +0200 16.07.2004, Herbert Poetzl wrote:
(dont' asky me why, I'm going to replace this crap
(I don't know why you call Mysql crap,
I know why, every sensible person knows why...
Tell us!
At 14:16 Uhr +0200 17.07.2004, loic d'Anterroches wrote:
At 10:19 Uhr +0200 17.07.2004, Dariush Pietrzak wrote:
At 15:09 Uhr +0200 16.07.2004, Herbert Poetzl wrote:
(dont' asky me why, I'm going to replace this crap
(I don't know why you call Mysql crap,
I know why, every sensible
At 21:36 Uhr + 12.07.2004, Liam Helmer wrote:
I think I liked the first one best. But, either of the first 2 are fine.
It was me who first said that they match user-mode linux better than
vserver. (Because the penguin is the mascot of the kernel and vserver
is not about running a kernel
Hi all
Following my suggestion (and little help), Herbert has put a
temporary start page at linux-vserver.org reminding of the impending
software patent situation and offering a link to some info about
which parties are best elected for the EU parlament in this regard.
We thus participate in a
At 10:35 Uhr +0200 17.05.2004, Markus Gsottberger wrote:
Error occurred during initialization of VM
Could not reserve enough space for code cache
The first thing I'd check is resource limits (type ulimit -a inside
vserver, start scripts).
___
Vserver
At 20:19 Uhr + 13.05.2004, Liam Helmer wrote:
I think that you're honestly better off creating some kind of pipe or
socket where the commands come through, which has a list of functions
that it can provide. That way you can have a list, and see if there's a
match for what's sent. It'd really
At 16:00 Uhr +1200 26.04.2004, Sam Vilain wrote:
Actually, my thoughts are that it would be nice to be able to
disable the SSH X11 forwarding from listening on any IPv4 address at
all.
Yes that would be nice.
The /unix xauth entry is for connection over the unix socket,
rather than TCP/IP.
Hello
There's a problem in the interaction between (ssh and xauth and
(linux-vserver or non-127.0.0.1 localhost ip's)):
If you use another ip than 127.0.0.1 (like say, 10.0.1.1) for
localhost purposes like me (and use a /etc/hosts file like this:
10.0.1.1 localhost
192.186.1.1
Somehow wall does seem to have some issues:
(- in my setup, it does only send messages to vserver users when run
inside the chroot containing my vserver tools. Ok my setup is very
special, but still I find it a bit odd, I can't explain it.)
- Sometimes vserver users get messages twice (where
At 14:17 Uhr -0400 15.04.2004, Gregory (Grisha) Trubetskoy wrote:
I may be missing something obvious, if so forgive me:
For some reason all my vservers resolve names using the main server's
/etc/hosts, not their own
Hm, not seen it myself, but if you use the host xyz command, it
does not
At 9:52 Uhr +0200 13.04.2004, Enrico Scholz wrote:
[EMAIL PROTECTED] (Christian Jaeger) writes:
1.- Not a problem of the utils but of my setup:
I have a setup where the vserver tools are inside a chroot, not on the
plain host. This is because I want to keep woody on the host, but the
alpha
At 9:52 Uhr +0200 13.04.2004, Enrico Scholz wrote:
I guess, 'tcpserver' closes standard input (fd 0) after creating the
sockets. When fd 0 is closed at program startup, the newly created
socket will get fd 0 and be closed.
Good guess, your advice has helped.
Thanks,
Christian
Mainly just wondering: why is there no real init process for each
vserver? At first, I thought that there was one, and that it's pid is
translated to 1 inside vserver context. But then I realized that the
process arguments, '[2]', is always representing the runlevel of the
host, not the vserver.
This is on a host with 2.4.25+grsec+vs1.3.8.
Multiple problems with reboot from inside a vserver running debian sarge (testing):
1.- Not a problem of the utils but of my setup:
I have a setup where the vserver tools are inside a chroot, not on the plain host.
This is because I want to keep
There's one more issue:
after rebooting a vserver running sarge, tcpserver (qmail) eats 100%
cpu. this only happens when rebooting it from inside (using reboot
-f), not when I vserver foo restart manually from the host.
strace shows this (looping):
rt_sigprocmask(SIG_BLOCK, [CHLD], NULL, 8) =
17 matches
Mail list logo
