-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks (again) for the bug report, passing it on to upstream.
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. I agree here, a simple failback to force-reload would be a simple solution. But on a long term it would be a good idea to catch the errors and report them back to the server and possibly attempt reconfigure later. - - S -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFpUqCqbb3MLg9dhwRAp55AJ9r/6mctyXwyrcjST2hyaYqgJZ3vACbBWI/ 50GjRofaqgvwQKHGZS3IOXo= =6dsD -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
