Trog wrote:
[cut]
Question: In what way does the arguments supplied to the configuration
option NotifyClamd (i.e. "/etc/rc.d/init.d/clamd reload") relate to the
specification of the argument to the configuration option NofityClamd
(i.e. /optional/config/file/path).
Answer: They don't.
something
On Wed, 2004-03-03 at 11:57, Andrzej Zawadzki wrote:
> Trog wrote:
> > On Wed, 2004-03-03 at 11:29, Andrzej Zawadzki wrote:
> >
> >
> >>#NotifyClamd [/optional/config/file/path]
> >>NotifyClamd /etc/rc.d/init.d/clamd reload
> >
> >
> > Whats this rubbish?
> > ---
Trog wrote:
On Wed, 2004-03-03 at 11:29, Andrzej Zawadzki wrote:
#NotifyClamd [/optional/config/file/path]
NotifyClamd /etc/rc.d/init.d/clamd reload
Whats this rubbish?
------
? Isn't this needed?
Clamd knows about new bases from freshclam anyway?
--
Andrzej
On Wed, 2004-03-03 at 11:29, Andrzej Zawadzki wrote:
> #NotifyClamd [/optional/config/file/path]
> NotifyClamd /etc/rc.d/init.d/clamd reload
Whats this rubbish?
------
-trog
signature.asc
Description: This is a digitally signed message part
[EMAIL PROTECTED] etc]# freshclam
ClamAV update process started at Wed Mar 3 11:56:30 2004
Reading CVD header (main.cvd): OK
main.cvd is up to date (version: 21, sigs: 20094, f-level: 1, builder:
tkojm)
Reading CVD header (daily.cvd): OK
Downloading daily.cvd [*]
daily.cvd updated (version: 158,
