Stephen Gran <[EMAIL PROTECTED]> writes: > This one time, at band camp, Daniel Pittman said: >> Oh, sorry, I must have missed that request: 'eth0 wlan0' > > Thanks, I figured as much, but it's nice to be sure. > >> Honestly, I was mostly surprised that it didn't just work; I expected >> the check to be "are any of these interfaces up"; something akin to >> this: >> >> ip addr | egrep 'eth0|wlan0' | egrep -q '\<UP\>' > > The problem that was originally addressed with this 'feature' is that > freshclam complains if it can't contact the mirrors. I don't think > keeping freshclam running when the default route goes away is doing the > right thing for the same problem. > > Or am I missing something? Not sure what other way to handle this at > the moment.
I don't think you can solve the problem of knowing which route, if any,
is needed for ClamAV to update the database.
I do think that if you offer multiple interfaces, though, people will
expect that the effect is that if any of them is up, freshclam will
continue to run.
I don't have a patch to offer, though, and I don't think it is worth
your investing a lot of time to try and resolve this.
Daniel
pgpYebOV2TtZx.pgp
Description: PGP signature
