Re: md_syslog (was Re: [Mimedefang] Woes following an OS upgrade)

2006-11-08 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 7 Nov 2006, Philip Prindeville wrote: I don't grasp the discussion about this topic, you can simply provide a md_syslog() wrapper for own :-/ I use md_syslog() extensively in MIMEDefang, no single %-sequence in them. Bye, - -- Steffen

[Mimedefang] Woes following an OS upgrade

2006-11-07 Thread Philip Prindeville
We were running FC3 on an x86_64 platform (good bang for the buck) and decided to finally upgrade to FC5... except that the FC3 to FC4 upgrade path doesn't really work, so we had to backup our disks, zap the system, install FC5 over it, and then copy back the content we wanted to keep. Hopefully,

md_syslog (was Re: [Mimedefang] Woes following an OS upgrade)

2006-11-07 Thread David F. Skoll
Philip Prindeville wrote: Oh... and in digging around, I saw: sub md_syslog ($$) { my($facility, $msg) = @_; [...] Hmm... Klunky. What about: sub md_syslog ($$;@) { my($facility, $fmt, @args) = @_; Except that now all callers of md_syslog have to change. That's no good.

Re: md_syslog (was Re: [Mimedefang] Woes following an OS upgrade)

2006-11-07 Thread Philip Prindeville
David F. Skoll wrote: Philip Prindeville wrote: Oh... and in digging around, I saw: sub md_syslog ($$) { my($facility, $msg) = @_; [...] Hmm... Klunky. What about: sub md_syslog ($$;@) { my($facility, $fmt, @args) = @_; Except that now all callers of

RE: [Mimedefang] Woes following an OS upgrade

2006-11-07 Thread Damrose, Mark
-Original Message- From: Philip Prindeville We were running FC3 on an x86_64 platform (good bang for the buck) and decided to finally upgrade to FC5... Lastly, I noticed that (you were probably wondering when this was going to actually be relevant to MdF, weren't you?) all of

Re: md_syslog (was Re: [Mimedefang] Woes following an OS upgrade)

2006-11-07 Thread David F. Skoll
Philip Prindeville wrote: Hmm. syslog() already has printf-style formatting... should the wrapper occlude that functionality? Yes, because it's superfluous in Perl. Just use variable interpolation directly. And what about callers that have to call sprintf directly if they want to handle

Re: [Mimedefang] Woes following an OS upgrade

2006-11-07 Thread Philip Prindeville
Damrose, Mark wrote: [snip] Yes. http://lists.roaringpenguin.com/pipermail/mimedefang/2006-September/030880.html The problem seems to be a combination of how MD initializes Sys::Syslog and Fedora's syslogd sub md_openlog ($$) { my($tag, $facility) = @_; $MDOpenLogCalled =

Re: md_syslog (was Re: [Mimedefang] Woes following an OS upgrade)

2006-11-07 Thread Philip Prindeville
David F. Skoll wrote: Philip Prindeville wrote: Hmm. syslog() already has printf-style formatting... should the wrapper occlude that functionality? Yes, because it's superfluous in Perl. Just use variable interpolation directly. Doesn't work with hex, or floats, etc. obviously.

Re: md_syslog (was Re: [Mimedefang] Woes following an OS upgrade)

2006-11-07 Thread David F. Skoll
Philip Prindeville wrote: Yes, because it's superfluous in Perl. Just use variable interpolation directly. Doesn't work with hex, or floats, etc. obviously. Just strings and integers. It works perfectly fine with floats. And hex, if you like: md_syslog($facility, foo . hex($number) .