Am 10.12.2015 um 16:44 schrieb Jóhann B. Guðmundsson:
On 12/10/2015 03:20 PM, Reindl Harald wrote:Am 10.12.2015 um 15:46 schrieb Jóhann B. Guðmundsson:If you are unaware of any other use case for itEnvironmentFile=-/etc/sysconfig/httpd ExecStart=/usr/sbin/httpd $OPTIONS -D FOREGROUND [root@testserver:~]$ cat /etc/sysconfig/httpd OPTIONS="-D testserver" Apache: <IfDefine testserver> Include "conf/local/testserver.conf" </IfDefine> and now you can use the same systemd-unit on a dozens of machines and include specific config snippets WITOUT touch the systemd-unit or *anything* else in the apache configurationYou apparently did not read or grasp what I said earlier. This is something you do via unit overwrite configuration snipped in conjunction with your Apache configuration changes not in an environment file.
this is something *i do not* with unit overwrite configuration by intention because i DO NOT want to touch ExecStart on any machine
perhaps it's time to start looking into obsoleting itdon't get me wrong but you sound once again like seek for changes to break users configuration to later blame users why they did not fix which ain't brokenYou cannot be gotten right. The follow up cleanup process in Fedora that I needed to conduct after the unit migration was completed, would have among other things obsoleted and removed those Fedora/RedHat specific environment files since it became clear immediately at that time that they had been obsoleted
cleanup whatever you want in Fedora, i don't use httpd or other server packages from the distribution at all - by removing "EnvironmentFile" from systemd you piss of users and sysadmins, not only distributions
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
