Am 05.02.2013 16:58, schrieb Jochen Schmitt: >> the same for updates of services: >> >> nothing would happen on a webserver with httpd if it would not be >> restarted at package-update which goes wrong if you are using PHP >> and packages of the dep-tree are not yet all updated which fails >> PHP to load, without the hardcoded restart httpd would happily >> continue to run with the old php-package from memory > > Question: Does it makes sense to collect all services which should > be restarted during the update process and restart the services after > all packages was updated? it would make MUCH more sense and if you are there and have removed the condrestart-crap from all of the SPEC-files you are in a position to make a global setting not restart any service which is what i want in case of a dist-upgrade * httpd is running * if it crashes -> Restart=always, RestartSec=1 * at all the better option as offline-upgrade * without restart services mostg things are running perfect * the upgrade takes 5 minutes * before restart i want manually verify grub-config and do cleanups * this cleanups take two minutes * after that i reboot the machine in the new system i am doing this since many years on many setups and rebuild all for me critical packages to prevent the restarts - BUT i still do not get this poor decision in a naive way mangle all SPEC-files
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel