>please try with mainstream 0.30.209, and if the
>issue persists, please file a bug report to savannah
>(and of course, let us know how it went :)
Unfortunately, I am a pure debian user and the latest
from unstable, it is only 0.30.208.4 and I have no
idea what is changed between these two.
FYI,
Hi,
I read in this list a few days ago about the local
127.0.0.x tricks of having internal communication
between vservers and it works well. However, I notice
a thing about the ip address:
1: lo: mtu 16436 qdisc noqueue
link/loopba
failed: Address already in use:
daemon abandoned
--- Herbert Poetzl <[EMAIL PROTECTED]> wrote:
> On Tue, May 31, 2005 at 02:06:49AM -0700, gary ng
> wrote:
> > Hi,
> >
> > I am having some strange problem with exim
Hi,
I am having some strange problem with exim4 in 1.2.10.
If I don't specify address/interface for it to bind,
it would try all address and stalled at 127.0.0.1. I
can only tell it to bind the assigned ip.
But for other service like sshd/slapd, it seems that
it works as expected, i.e. I can acce
Hi,
I just did a little more experiment and can now
establish vpn links with outside using either
pptp(Windows) or openvpn, from within a vserver.
As pointed out by other experts, this requires
CAP_NET_ADMIN and this right alone can allow the root
inside the jail to mess with most of the network
management(moving vserver from one
machine to another is much easier).
--- Herbert Poetzl <[EMAIL PROTECTED]> wrote:
> On Sat, May 28, 2005 at 04:42:04AM -0700, gary ng
> wrote:
> > Hi,
> >
> > I am testing out vserver(1.2.10 on 2.4, not ready
> for
> >
Hi,
I am testing out vserver(1.2.10 on 2.4, not ready for
2.6 yet because of stability issue unrelated to
vserver) and I am wondering what is the impact of
giving CAP_SYS_ADMIN to it.
Without it, I cannot mount within vserver but I see
mount as a legitimate use like mounting CIFS/NFS or
FUSE rela
