On Saturday 17 January 2004 14:19, Stefano Carraro wrote:
> Hello,
> during gentoo installation i've installed metalog as log service. Now, i've
> replaced it whith syslog-ng (replaced also in default runlevel). After
> doing this, all emerge will display this message:
[SNIP]
Have you done rc-upda
On Sat, 2004-01-17 at 13:29, Stefano Carraro wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Alle 14:14, sabato 17 gennaio 2004, Tom Wesley ha scritto:
>
> > emerge -C metalog
> > rm /etc/init.d/metalog
> > rc-update add syslog-ng boot
>
> yes, i've found the problem, but, following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alle 14:14, sabato 17 gennaio 2004, Tom Wesley ha scritto:
> emerge -C metalog
> rm /etc/init.d/metalog
> rc-update add syslog-ng boot
yes, i've found the problem, but, following the gentoo installation
instructions, i've added syslog to default run
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
resolved!
probably some mistake in command order. In /etc/init.d script for starting
metalog was present after unmerge. I've delete the script, removed and
reinserted from default runlevel the services depending from logger (vcron).
- --
=
On Sat, 2004-01-17 at 12:19, Stefano Carraro wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
> during gentoo installation i've installed metalog as log service. Now, i've
> replaced it whith syslog-ng (replaced also in default runlevel). After doing
> this, all emerge will di
Have you run "#rc-update del metalog" before add syslog-ng?
Cheers.
Stefano Carraro wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
during gentoo installation i've installed metalog as log service. Now, i've
replaced it whith syslog-ng (replaced also in default runlevel). After doing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
during gentoo installation i've installed metalog as log service. Now, i've
replaced it whith syslog-ng (replaced also in default runlevel). After doing
this, all emerge will display this message:
* Caching service dependencies...
* Servic
