On Tue, 27 May 2003, Sam Varshavchik wrote: > Ed Ravin writes: > > > I notice that syslogs from Courier programs at my shop do not include > > the PID of the process doing the logging. Is there any way to fix this? > > > > May 27 00:00:10 [EMAIL PROTECTED]/166.84.1.78 pop3d: LOGIN, user=joeb, > > ip=[::ffff:192.168.144.116] > > May 27 00:00:10 [EMAIL PROTECTED]/166.84.1.78 pop3d: LOGOUT, user=joeb, > > ip=[::ffff:192.168.144.116], top=0, retr=0 > > > What would you do with the pid anyway?
I too would *very* much like the pis in the syslog. Here's why: It lets me see which log messages go together. It is especially helpful when multiple message are coming in at once and you want to see what the IP of the spammer sending the message from [EMAIL PROTECTED] is. Right now, you cannot tell which smtpd process logs which message and there is no way to correlate an ip log message with a from/to log message. -- Joe Laffey | Want to convert subnet masks between different LAFFEY Computer Imaging | notations, or figure the number of IPs in a block? St. Louis, MO | Whatmask-It's FREE - www.laffeycomputer.com/wm.html ------------------------------------------------------------------------------ ------------------------------------------------------- This SF.net email is sponsored by: ObjectStore. If flattening out C++ or Java code to make your application fit in a relational database is painful, don't do it! Check out ObjectStore. Now part of Progress Software. http://www.objectstore.net/sourceforge _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
