Hi Guillem, thanks for your reply. On Mon, Oct 24, 2011 at 18:43, Guillem Jover <[email protected]> wrote: > severity 646425 wishlist > thanks > > Hi! > > On Mon, 2011-10-24 at 08:49:39 +0200, Sandro Tosi wrote: >> Package: dpkg >> Version: 1.15.8.8 >> Severity: important > >> there are some daemons that write messages only to stdout/err (so they >> don't have any "logging" capabilities by themselves). >> >> With the current classic execution line: >> >> start-stop-daemon --start --quiet --background --exec $DAEMON -- >> $DAEMON_OPTS >> >> those messages are lost, and they are the only form of debugging the daemon >> gives, without them we're forced to start it by-hand (hence the quite high >> severity). > > Well, I would not consider anything that requires --background a > proper daemon. As stated on the man page this is a last resort option > with its implied drawbacks. > >> Do you think it's feasable to add an option to redirect those messages to a >> file? something like --output /path/to/logfile , so we can look there for >> important msgs. > > While it would certainly be possible, I think it would be better to > modify such daemon to do proper daemonization and logging (either to a > file or via syslog), this usually should not amount to many lines of C > code.
Well, it's easier to say than do. Also, that's orthogonal to the problem: I can see your point for such badly written daemon, but redirecting stdout/err to /dev/null unconditionally is bad either :) Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
