Hi,
25.11.2009 20:16, 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 instal
> > 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 so
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.
>
> Th
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
h
