atom feed11 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: Courier Probl...
FromSent OnAttachments
Neil GruendingNov 26, 2000 4:22 pm 
Tabor J. WellsNov 26, 2000 6:30 pm 
Andrew McNamaraNov 26, 2000 7:09 pm 
Sam VarshavchikNov 26, 2000 7:47 pm 
Larry MooreNov 26, 2000 9:08 pm 
Neil GruendingNov 28, 2000 3:53 pm 
Sam VarshavchikNov 28, 2000 6:13 pm 
Brian KolaciNov 28, 2000 6:37 pm 
Sam VarshavchikNov 28, 2000 8:26 pm 
Neil GruendingNov 29, 2000 9:31 am 
Sam VarshavchikNov 29, 2000 2:55 pm 
Subject:Re: [courier-users] Re: Courier Problems When Rebooting Solaris
From:Neil Gruending (ne@gruending.net)
Date:Nov 29, 2000 9:31:20 am
List:net.sourceforge.lists.courier-users

So I'm SOL then? There's got to be a way to do this in solaris. I've got other deamons that can write to the console without blocking it...

Neil

On Wed, Nov 29, 2000 at 04:26:25AM +0000, Sam Varshavchik wrote:

Brian Kolaci writes:

> > Is this a valid fix? > > No. Errors from couriertcpd should not be allowed to disappear into a > bitbucket, just like that. Error output from couriertcpd may contain > valuable logging or debugging information, and every effort should be made > to throw them in front of someone's eyeballs. /dev/null certainly isn't > the right place.

I agree, how about using syslog ? Then the administrator can have it go to the console and/or system logfiles.

The syslog interface is a system call interface, to which you can't exactly attach a file descriptor. There is actually some code in there for a short utility to read from a pipe and dump all messages to syslog, but that will require some additional setup.