Before I assume no replies so far means that syslog support is broken or just plain not usable, please allow me to post my query a second time in hopes that a new set of eyes, with experience with Bacula and syslog, will see it...
Can anyone provide a sample of a messages resource destination specification using "syslog" that they know works? According to the Bacula doc, the syntax is supposed to be <destination> = <address> = <message-type1>, <message-type2>, ... where I can set "destination" to "syslog". The doc goes on to say the value of "address" will be ignored. The director's parser complains about an unknown message type if I follow this syntax, seemingly no matter what I put in for "address". What I can get the parser to accept is: syslog = <message-type1>, <message-type2>, ... But then I can't find anything in any of my Linux logs. The Bacula doc says its messages will be logged to the LOG_ERR facility. LOG_ERR is not a facility, it's a priority, AFAIK. LOG_ERR isn't actually a Linux syslog term, it's, I believe, a literal used in some logging support programming packages. So, I really have three questions: 1) Does the syslog destination really work for Bacula messages? 2) What facility and priority are actually being used for the syslog messages that are generated? 3) What is the correct syntax for a syslog destination in the messages resource? BTW, I'm running Bacula 1.38.2 on RHEL4 update 2. In advance, thanks! --Gary ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
