[systemd-devel] Query regarding "EnvironmentFile"
Lennart Poettering
lennart at poettering.net
Wed Dec 23 07:08:53 PST 2015
On Wed, 23.12.15 02:44, Reindl Harald (h.reindl at thelounge.net) wrote:
>
>
> Am 23.12.2015 um 01:24 schrieb Lennart Poettering:
> >On Thu, 10.12.15 16:20, Reindl Harald (h.reindl at thelounge.net) wrote:
> >>
> >>Am 10.12.2015 um 15:46 schrieb Jóhann B. Guðmundsson:
> >>>If you are unaware of any other use case for it
> >>
> >>EnvironmentFile=-/etc/sysconfig/httpd
> >>ExecStart=/usr/sbin/httpd $OPTIONS -D FOREGROUND
> >>
> >>[root at 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 configuration
> >
> >Well, there's not much difference in touching weird env var files or
> >the unit files themselves. I fail to see what the benefit of not
> >touching the unit files could be...
> >
> >Also, what you do above sounds like a job for unit file templates...
>
> since the functionality already exists and i am not a distribution "i am
> comfortable with it for years" should be enough - don't fix things which
> ain't broken
Well, the point I was making is that I am pretty sure EnvironmentFile=
*is* a broken concept... So yes, the distros should fix that, and stop
using it.
Lennart
--
Lennart Poettering, Red Hat
More information about the systemd-devel
mailing list