Ticket #134 (closed enhancement: fixed)

Opened 2 years ago

Last modified 2 years ago

Daemon should either not use stdout/stderr, flush stdout/stderr, or use unbuffered output

Reported by: julians Assigned to: mlandauer
Priority: major Milestone: 2007.03.23
Component: Daemon Version:
Keywords: Cc:

Description

We just discovered a problem when looking at the daemon output to stdout when it is piped through tee(1). In that case, status messages only make it into the log file or onto the tty if stdout is explicitly flushed after each output. That includes output terminated by a newline character.

The daemon should either explicitly flush the output file descriptors after each emitted message, configure those file descriptors to be unbuffered, or refrain from using stdout/stderr and instead use the rails logging mechanism for all output. The latter option is probably the most appropriate given that it's a daemon and (in the long run) meant to be run in the background anyway.

Change History

03/14/07 16:00:07 changed by julians

Made a change in r1071 so that file monitor will now write unbuffered to stdout.

03/19/07 10:08:05 changed by julians

  • status changed from new to closed.
  • resolution set to fixed.

This is addressed by the new daemon in r1078.