--On Saturday, March 29, 2008 1:30 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote:
> True, but Kenneth added additional logging beyond the debuging code. The additional stuff was just printf-debugging to figure out what was going wrong earlier. It can be excised or wrapped in if($Debug). > Also, There are two perl modules, Sys::Syslog and Unix::Syslog. I'm not > very familiar with perl and it's various modules, so I may be wrong, > but I think that Sys::Syslog is the more common, but Kenneth is using > Unix::Syslog. According to the FAQ at > <http://search.cpan.org/~mharnisch/Unix-Syslog-0.100/Syslog.pm>, > Unix::Syslog requires syslogd to be running on the local host, but > given that, it doesn't communicate with syslogd through a network > connection so it is not subject to the problems with that. I have no preference, as long as I can get an RPM/SRPM for it. CPAN qualifies, as there's a utility to encapsulate a CPAN module in an RPM. My concern is that I be able to see the output even if no mail is sent, so syslog is a natural solution. _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
