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

[Dag Wieers]

On Thu, 28 Feb 2008, Andreas Rogge wrote:

> Dag Wieers schrieb:
>
>> 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 ?
>
> I don't know where I read it, but somebody proposed not to output anything on 
> rpm operations.
> The problem is that you never know where your output will actually go. For 
> example, if you use yum-updatesd, you will probably never see that output.

Right. That used to be the default, but remember that even Red Hat now 
does it for openssh. :-)

Of course if you do things in automated ways it is your responsibility 
that you see the output. If yum-updatesd is sending my .rpmsave/.rpmorig 
information to /dev/null, than I would never use yum-updatesd ever.

In fact, RPMs can provide output, but they should not ask for input. That 
has always been the important difference between RPM packages and what 
Debian did.


> IMO people should know that services will be restarted on an upgrade, simply 
> because that's the way it works.

It is not always that black and white. Not everybody knows that a service 
is being restarted (and not always are services restarted when you do 
condrestart). Also, if you install xinetd-services it reloads xinetd, but 
what if xinetd because of that bails out ?

Also if you are working in a big team, it is possible that not everybody 
is aware of what services are enabled and also in that case it is useful 
to see that the service has been restarted.


> For your example: if a service is misconfigured and it then breaks on an 
> upgrade, I don't think it is a problem with the rpm, but a problem with the 
> admin. If one really wants to catch such an issue, you'd have to write a 
> pre-script that checks wheter the configuration is ok and stops the upgrade 
> otherwise.

That is impossible to guarantee. I much rather play safe and let the 
sysadmin know we have restarted a service and it might have failed. So at 
least he can check it.


> However, that solution doesn't really look good to me. So what we have 
> currently should probably be enough.

No, I am convinced that we need to show service restarts even though that 
was not the policy in the past. In a discussion a year ago others agreed 
to it as well.

What do other people think ?

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