Summary: | GNAP: Network fails to come up if syslog-ng is set to remote logging | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | andy |
Component: | GNAP | Assignee: | Gentoo Network Appliance Bugs <gnap> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
andy
2006-03-02 14:49:09 UTC
Interesting :) Can't change it in a release candidate phase, but I'll try to find a good solution for 2.0.1 afterwards. I had some similar issues when adding Asterisk to the mix. Uberlord helped debug the problem and the fixes are now in the latest ~x86 baselayout (not sure wether it is stable yet but it works fine on my boxen). I tried gnap-2.0 from portage today and it seems like the bug still exists. Does anybody know how to fix or workaround this? I get the problem because syslog needs network, network starts after iptables and iptables needs syslog. This is on normal Gentoo though, using openrc, but maybe it's the same. I removed the dependency on syslog from iptables. The GNAP project has been discontinued, its removal was acknowledged by steev. If you need to, you can contact the Gentoo Embedded project; more information about the Gentoo Embedded project can be found on the following link: http://www.gentoo.org/proj/en/base/embedded/ This removal happens as part of project cleanup by the Gentoo Council's members. |