Hi, Thanks for the quick look. Thats What I thought anyway by reading the announcement. which means deleting the directories will bring the system in the sate the service unit author or the admin intended, sweet...
Let see where this concept evolves in terms of general settings for a particular service unit... Is this the intention to go into the config management direction? Holger > > "These settings are stored persistently on disk" goes to. If yo have such > > setting somewhere else as back in the unit, how do you know those settings > > exists. If they go back into the unit you obviously overwrite the bootstrap > > default setting in the unit... may it goes into the sytemd/unite.service.d/ > > ? > > > > Feedback would be welcome ;-) > > Runtime changes go into > /run/systemd/system/<unit_id>.d/50-<unit_name>.conf; persistent > into /etc/systemd/system/<unit_id>.d/50-<unit_name>.conf. I'm no sure what's > the > difference between ID and name is, I'm just looking at unit_write_drop_in() > function. -- _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
