Bug 74813 - syslog facility wrong on startup
Summary: syslog facility wrong on startup
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Mario Sergio Fujikawa Ferreira
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-07 12:40 UTC by Helge Oldach
Modified: 2004-12-14 13:46 UTC (History)
1 user (show)

See Also:


Attachments
file.diff (878 bytes, patch)
2004-12-07 12:40 UTC, Helge Oldach
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Helge Oldach 2004-12-07 12:40:25 UTC
Upon startup of qpopper the syslog facility is set to LOCAL0. This is
true even if the -y flag is specified on the command line, pointing to a
different syslog facility.

This causes startup and termination information to be logged wrongly:

Dec  7 13:23:50 sep qpopper[89470]: qpopper: Server: cleaning up and exiting normally
Dec  7 13:23:54 sep qpopper[89493]: qpopper: Server: listening on [::]:995
Dec  7 13:23:54 sep qpopper[89493]: qpopper: Server: listening on 0.0.0.0:995

The patch below attempts to read the -y flag very early in in the
startup process (similar to the -d and -t flags).
Comment 1 Volker Stolz freebsd_committer 2004-12-07 15:20:23 UTC
Responsible Changed
From-To: freebsd-ports-bugs->lioux

Over to maintainer
Comment 2 Mario Sergio Fujikawa Ferreira freebsd_committer 2004-12-14 13:46:11 UTC
State Changed
From-To: open->closed

Committed, thanks!