smsd only logs to stderr before forking

Bug #258282 reported by Morten Brekkevold
2
Affects Status Importance Assigned to Milestone
Network Administration Visualized
Fix Released
Medium
Stein Magnus Jodal

Bug Description

The sms daemon doesn't start logging to it's log file until it has forked
off a daemon process. Any errors during startup will not be logged or
showed to users because stderr is redirected to /dev/null by the nav start
command.

The process should always log to smsd.log.

[http://sourceforge.net/tracker/index.php?func=detail&aid=1822737&group_id=107608&atid=648170]

Revision history for this message
Thomas Adamcik (adamcik) wrote :

Originator: NO

Since the new alertengoine code uses the same functions to daemonize it is
also affected

Changed in nav:
milestone: v3.3 → v3.5
Changed in nav:
milestone: v3.5 → v3.5.0
Revision history for this message
Stein Magnus Jodal (jodal) wrote :

Morten: This bug is fixed in revision 4235:9eae30b73754 in the default branch.

Thomas: The fix did not touch nav.daemon, but a fix relevant to you and alertengine was made to smsd and nav.daemon in revision 4237:48bf15551466 in the default branch to make them adhere to settings in logging.conf.

Changed in nav:
status: Confirmed → Fix Committed
Changed in nav:
milestone: v3.5.0 → v3.4.3
Changed in nav:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.