Hi,

24.11.2009 17:20, Timo Neuvonen wrote:
> After updating two Bacula 3.0.2 servers to version 3.0.3 both of them 
> started to claim this:
> 
> ----
> /etc/cron.daily/0logwatch:
> 
> Cannot find shared script applybaculadate
> ----
> 
> Both are 64-bit CentOS5 systems, rpm installations.
> 
> This is obviously due to some packaging specific change in log file 
> handling.
> Has anyone else met this, any ideas how to start troublesoot?
> 
> Same day I also updated these systems from CentOS 5.3 to 5.4

Check if you've got files that look like they are logwatch-related in 
/etc/log.d/ - I was pointed to this issue by a customer and haven't 
investigated yet, but it looks like a packaging issue.

Ideally, you'd only have to move those files to their correct 
locations in /etc/logwatch/ and everything's fine.

Cheers,

Arno

> 
> Regards,
> Timo
> 
> 
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
> 

-- 
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
www.its-lehmann.de

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users