On Mon, 19 Jan 2004, Dan Melomedman wrote: > Dan Melomedman wrote: > > Sam Varshavchik wrote: > > > Dan Melomedman writes: > > > > > > >Mr. Sam, which 'logger' directive did you mention the last time? I want > > > >courierd's logs sent to a program, not syslog. Is this functionality > > > >supported? Thanks. > > > > > > Nope, not in courierd's case. Logs from other daemons could be easily > > > redirected, but not courierd's. > > > > Wouldn't this be a useful feature to have? Syslog is ridiculously slow > > among other things. > > Also, the design could be much more flexible if courierd ran in > the foreground, and simply wrote logs to stderr or stdout. Then a > sysadmin could use supervisors and loggers of his/her choice instead of > relying on the broken syslog, and the unriliable PID/lock files > mechanisms.
In general, I agree. I use freedt (a *free* replacement for daemontools), and very much subscribe to that method of process management. I prefer "daemons" to [be able to] run in the foreground and write to stderr or stdout for their logging. -- Ensign Walnut approaches Dr. Crusher with caution... Jon Nelson <[EMAIL PROTECTED]> C and Python Code Gardener ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
