>>>>> "Sami" == Sami Haahtinen <[EMAIL PROTECTED]> writes:
Sami> Thanks (again) for the bug report, passing it on to upstream. Sami> jacques Normand wrote: >> The call used to restart a service is wrong >> (/etc/init.d/<service> reload). The policy states that the >> support of the reload is optional. And when bcfg2 fails to reload >> a service, it does not report it anywhere. Which is why I >> consider this bug as important. It could very well lead to a >> critical service falsely updated and left in an unsecure >> situation. Using the force-reload (which is mandatory) when >> reload fails would be a good fix. Sami> I agree here, a simple failback to force-reload would be a Sami> simple solution. But on a long term it would be a good idea to Sami> catch the errors and report them back to the server and Sami> possibly attempt reconfigure later. Should we change the default to force-reload for debinit? it can be overridden by using the reload attribute for services. If force-reload is mandatory, then we should probably use it. Thoughts? We have an analogous issue with fedora, except force-reload -> condrestart, so I was thinking about changing it chkconfig to use condrestart... -nld
pgpNBwyTi5bUZ.pgp
Description: PGP signature
