Further to this, here's the relevant bits from one of my syslog-ng
files. A word of note: the devices at /vservers/.devs//dev are
bind mounted into the vserver by another part of the startup... you
could change them safely to /vservsers//dev/log. This whole
configuration is generated with a script.
Hi Enrico,
Am Donnerstag, den 30.12.2004, 01:13 +0100 schrieb Enrico Scholz:
> [EMAIL PROTECTED] ("Kilian Krause") writes:
>
> >> >> [ ... util-vserver.spec ...]
> >> > Hrmpf. Then can we just not delete it in make clean?
> >>
> >> I will think about this; but I still do not understand the prob
Hi Herbert,
> please keep this discussion going (maybe some typical
> ipv6 examples or so?) so we can get a feeling for it.
what kind of "typical example" are you asking for? The default IPv6
address style is quite forward to the ipv4 notation (well, same logic
applies, but a slightly changed not
[EMAIL PROTECTED] ("Kilian Krause") writes:
>> >> [ ... util-vserver.spec ...]
>> > Hrmpf. Then can we just not delete it in make clean?
>>
>> I will think about this; but I still do not understand the problem
>> there.
>
> very easy to tell. You're talking about "what configure builds, make
> c
Hi Herbert,
Am Mittwoch, den 29.12.2004, 00:01 +0100 schrieb Herbert Poetzl:
> > > chkconfig --del network
> > >
> > > and it removes all the links from the various runlevels
> > > so that 'network' isn't started anymore ...
> >
> > The problem is that as soon as the next update to the "network
Hi Enrico,
Am Dienstag, den 28.12.2004, 03:49 +0100 schrieb Enrico Scholz:
> >> [ ... util-vserver.spec ...]
> >> > Sounds like maybe it shouldn't be shipped in the release tarball
> >> > then..
> >>
> >> No, it must be shipped. Else 'rpmbuild -ta util-vserver...tar.bz2' would
> >> not work anymo
