[gentoo-user] syslog problem....

[gentoo-user] syslog problem....

[David Corbin]

When I try to start exim, I get this:

 * Caching service dependencies ...
 *  Service 'sysklogd' already provided by 'logger'!;
 *  Not adding service 'syslog-ng'...                                                    
[ ok ]
 * sysklogd -> start: syslogd ...
/sbin/start-stop-daemon: stat /usr/sbin/syslogd: No such file or directory (No 
such file or directory)
 * Failed to start syslogd                                                               
[ !! ]
 * ERROR:  cannot start exim as sysklogd could not start

I have syslog-ng installed, and don't understand why it's trying to load 
sysklogd...pointers welcome.

Thanks
David
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[Richard Fish]

On 12/7/06, David Corbin <gentoo.org@machturtle.com> wrote:
> When I try to start exim, I get this:
>
>  * Caching service dependencies ...
>  *  Service 'sysklogd' already provided by 'logger'!;
>  *  Not adding service 'syslog-ng'...
> [ ok ]
>  * sysklogd -> start: syslogd ...
> /sbin/start-stop-daemon: stat /usr/sbin/syslogd: No such file or directory (No
> such file or directory)
>  * Failed to start syslogd

I don't have exim installed, but I'm guessing it depends on "logger",
which can be provided by either sysklogd or syslog-ng.

Probably:

1. You had sysklogd installed at one point (thus got an init file for it)
2. You emerge -C'd it (thus why /usr/sbin/syslogd doesn't exist)
3. You have /etc in CONFIG_PROTECT but don't have /etc/init.d in
CONFIG_PROTECT_MASK, so portage left the sysklogd init file on your
system.

I'm guessing you should be able to resolve this with:

1. rc-update -d sysklogd
2. rm /etc/init.d/sysklogd

Then add /etc/init.d to CONFIG_PROTECT_MASK in /etc/make.conf if you
want portage to automatically remove init files when you remove the
associated package.

HTH,
-Richard
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[David Corbin]

On Friday 08 December 2006 00:43, Richard Fish wrote:
> On 12/7/06, David Corbin <gentoo.org@machturtle.com> wrote:
>
> I don't have exim installed, but I'm guessing it depends on "logger",

It does.

> which can be provided by either sysklogd or syslog-ng.
>
> Probably:
>
> 1. You had sysklogd installed at one point (thus got an init file for it)

I don't think I did. It's a pretty new install.  And there is not init file fo 
rit.

> 2. You emerge -C'd it (thus why /usr/sbin/syslogd doesn't exist)
> 3. You have /etc in CONFIG_PROTECT but don't have /etc/init.d in
> CONFIG_PROTECT_MASK, so portage left the sysklogd init file on your
> system.
>
> I'm guessing you should be able to resolve this with:
>
> 1. rc-update -d sysklogd

 * 'sysklogd' not found in any of the specified runlevels

> 2. rm /etc/init.d/sysklogd
>


When an initscript says it depends on logger, how does runscript find out what 
tool provides logger?

David
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[Richard Fish]

On 12/8/06, David Corbin <gentoo.org@machturtle.com> wrote:
> When an initscript says it depends on logger, how does runscript find out what
> tool provides logger?

AFAIK, the "provide" settings in the init scripts themselves. Try:
grep -E "provide.*logger" /etc/init.d/*
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[David Corbin]

On Friday 08 December 2006 19:58, Richard Fish wrote:
> On 12/8/06, David Corbin <gentoo.org@machturtle.com> wrote:
> > When an initscript says it depends on logger, how does runscript find out
> > what tool provides logger?
>
> AFAIK, the "provide" settings in the init scripts themselves. 

I understand that's where it's defined, but what I meant was how does it find 
it.  Surely it's not running every script each time somebody depends on 
something.


> Try: 
> grep -E "provide.*logger" /etc/init.d/*

dcorbin init.d # grep -E "provide.*logger" /etc/init.d/*
/etc/init.d/syslog-ng:  provide logger

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[David Corbin]

On Friday 08 December 2006 19:58, Richard Fish wrote:
> On 12/8/06, David Corbin <gentoo.org@machturtle.com> wrote:
> > When an initscript says it depends on logger, how does runscript find out
> > what tool provides logger?
>
> AFAIK, the "provide" settings in the init scripts themselves. 

I understand that's where it's defined, but what I meant was how does it find 
it.  Surely it's not running every script each time somebody depends on 
something.


> Try: 
> grep -E "provide.*logger" /etc/init.d/*

dcorbin init.d # grep -E "provide.*logger" /etc/init.d/*
/etc/init.d/syslog-ng:  provide logger

-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[David Corbin]

On Saturday 09 December 2006 06:57, David Corbin wrote:
> On Friday 08 December 2006 19:58, Richard Fish wrote:
> > On 12/8/06, David Corbin <gentoo.org@machturtle.com> wrote:
> > > When an initscript says it depends on logger, how does runscript find
> > > out what tool provides logger?
> >
> > AFAIK, the "provide" settings in the init scripts themselves.
>
> I understand that's where it's defined, but what I meant was how does it
> find it.  Surely it's not running every script each time somebody depends
> on something.
>
> > Try:
> > grep -E "provide.*logger" /etc/init.d/*
>
> dcorbin init.d # grep -E "provide.*logger" /etc/init.d/*
> /etc/init.d/syslog-ng:  provide logger

I've gone ahead and removed syslog-ng and installed sysklogd.  Working fine 
now, and I'm happy, though it would be nice to understand...
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[David Corbin]

On Saturday 09 December 2006 06:57, David Corbin wrote:
> On Friday 08 December 2006 19:58, Richard Fish wrote:
> > On 12/8/06, David Corbin <gentoo.org@machturtle.com> wrote:
> > > When an initscript says it depends on logger, how does runscript find
> > > out what tool provides logger?
> >
> > AFAIK, the "provide" settings in the init scripts themselves.
>
> I understand that's where it's defined, but what I meant was how does it
> find it.  Surely it's not running every script each time somebody depends
> on something.
>
> > Try:
> > grep -E "provide.*logger" /etc/init.d/*
>
> dcorbin init.d # grep -E "provide.*logger" /etc/init.d/*
> /etc/init.d/syslog-ng:  provide logger

I've gone ahead and removed syslog-ng and installed sysklogd.  Working fine 
now, and I'm happy, though it would be nice to understand...
-- 
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] syslog problem....

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 608 bytes --]

On Sat, 9 Dec 2006 06:57:14 -0500, David Corbin wrote:

> > AFAIK, the "provide" settings in the init scripts themselves.   
> 
> I understand that's where it's defined, but what I meant was how does
> it find it.  Surely it's not running every script each time somebody
> depends on something.

The information is cached, sometimes when you start a service from the
command line you'll see a message like "caching service dependencies".


-- 
Neil Bothwick

*Libra*: /(Sept 23--Oct 23)/ An unfortunate typo on your application
results in your being accepted into the Legion Of Superherpes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]