Sorry, misread your post.  

Yes, the current way that the client does logging is going to make system and 
backup admin more difficult.  Because of the way that it does logging now, 
there's going to be a lot of garbage in the log files that networker writes to. 
 for the life of me, I can't think of a good reason for them to make this kind 
of change.  All they've done is potentially broken alot of people scripts.  
I've been reading several posts where alot of the things that they've done in 
recent releases are breaking things (and I know from first hand experience 
also).

BSD system used to have a way to filter facilities so that you could separate 
logs based on tags, but the Linux version of syslog doesn't do that.  I haven't 
a reason to learn syslog-ng yet, but I think that this issue with networker is 
going to force me to.

Dave

+----------------------------------------------------------------------
|This was sent by david.fields AT acs-inc DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER