one log for each module

tim.conway at tim.conway at
Sat Oct 27 02:59:08 EST 2001

Well, Ivan, it's not in the code, at least, not yet.  How about this for a 
simple solution.  use syslog.  Choose an unused facility.  make the 
destination a program.  Perl is probably the best tool for this. 
filehandle named for module called.  they can be generated on the fly. the 
process id is used to direct the "wrote somany bytes" lines to the right 
file.  You could do it with a growing array of filehandles, or simply 
opening and closing the filehandles in append mode, as needed.  I prefer 
the second one, as it makes it possible to manage the logs without 
restarting.  Of course, you'll have one log program running continuously, 
with a line feeder called by syslog.

Actually, it would probably be easier to just make the syslog destination 
a fifo, and read that from the perl script.  I've had bad luck with fifos, 
but maybe perl does a better job handling them than the shell scripts i 
was using.
Good luck.

Tim Conway
tim.conway at
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(nnnnnnnnnnnn, 
".\n" '
"There are some who call me.... Tim?"

Ivan Renedo <ivan at>
Sent by: rsync-admin at
10/26/2001 10:08 AM
Please respond to ivan

        To:     rsync at
        cc:     (bcc: Tim Conway/LMT/SC/PHILIPS)
        Subject:        one log for each module

There are some way to have a log for each module?
If there aren't, it should be a a great functionality for maintaining the 
Thanks for the help and continue with this great application !

-------------- next part --------------
HTML attachment scrubbed and removed

More information about the rsync mailing list