Re: trend-update.pl v1.00 released

Alain Fauconnet wrote:
> Trend pattern numbers 2.160 and 2.180 have passed and the  version  of
> trend-update.pl in use on our own mail  server  runs  smoothly,  so  I
> think that I can assume that Trend's transition to NPF is done now, and
> I can release my script for whomever wants it.
[snip]

This is very cool and pretty much what I've been looking for. I've got a 
VirusWall that's scanning HTTP, but I want to use amavisd-new and 
trophie to scan emails.

I see that you handle reloading and/or restarting of trophie in your 
script. But what about the VirusWall itself or, more specifically and in 
my case, the HTTP scanner? Do you know if it needs to be signalled 
and/or restarted as well? Or does it notice that the signature file 
and/or scanning engine has/have changed? A colleague of mine recently 
updated the scanning engine on a running VirusWall and said that he saw 
very strange entires in the VirusWall's log.

However, I just ran trend-update.pl on the machine in question and it 
appears that the HTTP scanner is still up and running...

Alternatively, I could of course have trophie/trend-update.pl and the 
VirusWall use entirely separate directories to store the scanning engine 
and signature files. I'd prefer to avoid this redundancy, though.

Cheers,
Tobias