First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 13541
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Martin Holzer (RETIRED) <mholzer@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Alexander Holler <aholler@gentoo.de>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 13541 depends on: Show dependency tree
Bug 13541 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2003-01-08 22:06 0000 
see above. 
 
Regards, 
 
Alexander

------- Comment #1 From Martin Holzer (RETIRED) 2003-01-09 06:34:24 0000 ------- 
fixed in cvs

thx

------- Comment #2 From Jason Wever (RETIRED) 2003-01-09 21:08:21 0000 ------- 
"use dns logger" now causes an error where rc-update and the mechanism that
loads init'd scripts on start think that ntpd is trying to do generic logging,
and it's causing a confliction with the sysloggers (sysklogd in my case).  The
error I'm seeing is this

"excelsior root # rc-update add ntpd default
 * ntpd added to runlevel default...
 * Caching service dependencies...
 * PROVIDE:  it usually is not a good idea to have more than one
  [ ok ]     service provide the same virtual service (logger)!
 * rc-update complete.
"

------- Comment #3 From Alexander Holler 2003-01-09 21:20:23 0000 ------- 
If this bug really depends on the use dns logger line, then runscript is the
failure.  use != provide  I think this is totally independ on that use line in
ntp and you have emerged two loggers. Then you will get such an message.

------- Comment #4 From Jason Wever (RETIRED) 2003-01-09 21:52:47 0000 ------- 
I think you're probably right Alexander, my whole init.d deal seems to have
gone
haywire on this machine.  I'm putting htis back to resolved:fixed. Sorry for
the
confusion
First Last Prev Next    No search results available      Search page      Enter new bug