Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 154097 - syslog-ng should start when configured to log network events, even when no network service has started
Summary: syslog-ng should start when configured to log network events, even when no ne...
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High enhancement (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-04 22:02 UTC by Karsten Baumgarten
Modified: 2006-11-05 01:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karsten Baumgarten 2006-11-04 22:02:46 UTC
The syslog-ng init script defines a conditional dependency on "net", whenever it detects that syslog-ng is configured to log network events (sources/destinations that contain tcp/udp). While this makes perfect sense for environments with fixed connections, it prevents the startup of the logging service for others, using transient connections (or in my case, simply forget to plug in the network cable). Since syslog-ng starts without "net", even when configured to log network events, I think the conditional dependency should be removed. Having no syslog daemon is worse than having one that cannot log network events, that will never happen. :)
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2006-11-05 00:56:35 UTC
Set RC_NET_STRICT_CHECKING to "lo" in /etc/conf.d/rc if you don't care whether syslog-ng will log correctly or not.
Comment 2 Karsten Baumgarten 2006-11-05 01:16:25 UTC
(In reply to comment #1)
> Set RC_NET_STRICT_CHECKING to "lo" in /etc/conf.d/rc if you don't care whether
> syslog-ng will log correctly or not.
> 

Thanks for the hint!