BUG: clamav packages badly broken

[Michael Schwendt]

On Sat, 29 Dec 2007 11:38:24 -0800, Florin Andrei wrote:

> Michael Schwendt wrote:
> > 
> > Is setting up Samba or ntpd so much easier?
> 
> Are you living in the same universe like everyone else?
>
> ntp can be launched immediately after it's installed. "service ntpd 
> start" and it's working already.

Because these days a default setup is provided for it already at
firstboot-time (and hence the same defaults can be provided in the package
already, too). And it's a system-wide service.

# yum -y install openvpn
[...]
# service openvpn start
Starting openvpn:                                          [  OK  ]
# service openvpn start
Starting openvpn:                                          [  OK  ]
# service openvpn start
Starting openvpn:                                          [  OK  ]
[...]
# service openvpn status
openvpn: service not started
[...]
# service openvpn stop
Shutting down openvpn:                                     [  OK  ]
# service openvpn stop
Shutting down openvpn:                                     [  OK  ]
# service openvpn stop
Shutting down openvpn:                                     [  OK  ]

Hint: Read the initscript header to find out what is missing.

# yum -y install hddtemp
[...]
# service hddtemp start
Unconfigured: hddtemp, see /etc/sysconfig/hddtemp:         [FAILED]

> Samba may require setting up the workgroup at least, a couple more 
> config items at most, then it's good to go. Or you can simply launch it 
> as is and it will still work, albeit using the default workgroup. This 
> is acceptable. This is very different from the situation with the EPEL 
> clamav packages.

Ah, you would probably call the default openldap server setup
"acceptable", too...  truth is, these services require somebody to edit
the config files if you want more than an "[  OK  ]" to make you happy.