Summary: | net-misc/ntp-4.2.4p7-r1 switches syslog facility | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Łukasz Stelmach <stlman> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | mmokrejs |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Łukasz Stelmach
2010-02-28 16:00:31 UTC
That compatibility blurb comes from avahi; stick AVAHI_COMPAT_NOWARN="1" before the start-stop-daemon call to make it shut up. The blurb is not a problem at all. Take a closer look at sendto() calls. Before the blurb the priority > 24 (LOG_DAEMON) then just after the first avahi warning the syslog messages goes as LOG_USER. Yes, I understand - I'm suggesting that stopping the blurb from getting spit out in the first place could make avahi shut up and thus could work around the syslog switching. Indeed it does help. However it seems like bug anyway. does it only happen when using USE=zeroconf ? I don't know. It does happen when I USE=zeroconf and it doesn't when I don't. However, I haven't investigated it more deeply, it seems to be quite obvious that libavahi reopens syslog with different facility. |