[suggest] Clamav should not require a specific clamav-db version

[Dag Wieers]

On Thu, 28 Feb 2008, Federico Simoncelli wrote:

> On Wed, Feb 27, 2008 at 12:41 PM, Dag Wieers <dag at wieers.com> wrote:
>> On Wed, 27 Feb 2008, Federico Simoncelli wrote:
>> > I'm using the clamav/clamd packages and I think clamav shouldn't
>> > strictly depend on the same clamav-db version.
>>
>>  You are completely correct in analysis and solution. Thanks for making it
>>  simple to agree :-)
>
> I also suggest to modify the spec file to restart the freshclam daemon
> if needed. I added this fix a long time ago because sometimes
> freshclam was hanging after a clamav/clamd update. I honestly don't
> have any more information about this issue and how to reproduce it.
>
> -%postun -p /sbin/ldconfig
> +%postun
> +/sbin/ldconfig
> +/sbin/service freshclam condrestart &>/dev/null || :
>
> I'm sure it can be improved (check for a clamav package still installed).

I see no problem doing that, although I am in favor (contrary to what we 
are currently doing) to display the output of started, stopped and 
restarted services. I think it is too important that you know that a 
service has been restarted and whether that worked or not.

Imagine doing an condrestart behind the back but the service trips on a 
configuration change from the past although the service was not restarted 
for a long time. I think we are providing a bad service if for that reason 
the service is down and may not be noticed until complaints come in...

Although until now all RPM packages send output to /dev/null, my opinion 
is that we should show it. (Except maybe when you do an uninstall, which 
implies that you stop the service anyway)

What do you think ?
-- 
--   dag wieers,  dag at wieers.com,  http://dag.wieers.com/   --
[Any errors in spelling, tact or fact are transmission errors]