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 server. Thanks for the help and continue with this great application !

Re: one log for each module

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

Re: one log for each module

On Fri, Oct 26, 2001 at 06:08:55PM +0200, Ivan Renedo wrote: 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 server. Thanks for the help and continue with this great application ! Currently the log file option is a

2.4.7p1 protocol differences?

Hi all, rsync-2.4.6 has been running for quite a while with no problems, until about a week ago when for some reason it blocked on the same host ever time. I use it to backup about thirty hosts to my backup server, but for some reason it's illiciting that blocking bug that some people

avoid different versions

Is their a way or a quick bash script anyone has that would first take down the files, but after would look through the list downloaded and any duplicate file with some version, the highest version would be taken and the lower versions deleted? -- Jason G Helfman