smsd only logs to stderr before forking
Bug #258282 reported by
Morten Brekkevold
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://
Changed in nav: | |
milestone: | v3.3 → v3.5 |
Changed in nav: | |
milestone: | v3.5 → v3.5.0 |
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.
Originator: NO
Since the new alertengoine code uses the same functions to daemonize it is
also affected