Bug 661282

Summary:	restarting daemons for sysconfig changes
Product:	[Fedora] Fedora	Reporter:	Marcela Mašláňová <mmaslano>
Component:	systemd	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	k.georgiou, lpoetter, metherid, mschmidt, notting, plautrba
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-03-04 04:09:43 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcela Mašláňová 2010-12-08 12:05:38 UTC

I had bug reports about restarting daemon because of changes in sysconfig file. Imagine that you have cron daemon running on cluster or with home's through LDAP. After every restart is possible that something goes wrong like LDAP user's won't be found. Also I don't think it's wise reloading all daemons. Some could take new options immediately, some after restart,... I will have troubles only with cron, but what about more important services, where system administrator have to restart daemons?

Please revert this behaviour.

Reproducer:
change /etc/sysconfig/crond
systemctl --system daemon-reload
service crond restart

Version:
systemd-15-1.fc15.x86_64

Comment 1 Lennart Poettering 2011-01-04 23:35:34 UTC

Hmm, we probably should read that information when spawning a service, not already when loading the configuration.

Comment 2 Lennart Poettering 2011-03-04 04:09:43 UTC

systemd git now reads those env config files at process spwan time, not already when systemd reads its own configuration. This should resolve the issue.

Upload to F15 follows shortly.