Stephen Gran <[EMAIL PROTECTED]> writes: > This one time, at band camp, Stephen Gran said: >> This one time, at band camp, Daniel Pittman said: >> > When I bring down the wlan0 interface on my machine, freshclam is >> > stopped. This happens even if I had a working connection on eth0, which >> > was up the whole time. >> > >> > This isn't nice, because it can result in database updates stopping >> > unexpectedly for people if they have more than one way to reach the >> > Internet... >> >> What are the contents of /var/lib/clamav/interface? If you have both >> interfaces listed there, then I am afraid both will affect freshclam for >> now. >> >> I will try to find a way to make it not down freshclam if one of the >> interfaces is up, but as always, patches are welcome :) > > OK, I can only think of one way to avoid this, and that is by checking > for the default route. That may not make sense for some people (they > could concievably be getting their database definitions from a LAN > machine, and this machine has a route to the LAN and the internet, or > something), but it seems like making sure that we only down freshclam > when it is the default route going down does make some sense. > > Do you feel like this is reasonable, or have a different idea? Could > you also please let me know the know the contents of > /var/lib/clamav/interface, as I asked?
Oh, sorry, I must have missed that request: 'eth0 wlan0'
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\>'
Daniel
pgpNrSuCXDQ7d.pgp
Description: PGP signature
