Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:39 schrieb Manuel Amador (Rudd-O): On 12/26/2015 07:28 PM, Reindl Harald wrote: my infrastructure is most likely better managed than anyone leses So says the person with a limited perspective and a refusal to learn modern tools and processes the person with a limited

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/26/2015 06:44 PM, Reindl Harald wrote: > > > Am 26.12.2015 um 19:41 schrieb Manuel Amador (Rudd-O): >> On 12/23/2015 10:40 PM, Reindl Harald wrote: >> >> Nobody is forcing you to change anything from your configuration > > Johann would if he had the power to do so Aren't you glad he

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/10/2015 11:42 AM, Simon McVittie wrote: > The approach I try to follow in dbus is that options that should be > changed by another package (such as default security policies) go in a > configuration file, or more recently a file in /usr/share; options that > should be changed by the sysadmin

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/26/2015 06:58 PM, Reindl Harald wrote: > > uhm - "EnvironmentFile" don't change often and so reload is possible > all the time I never said you couldn't reload. I said that reload would not enact your environment file changes. Are you having trouble understanding what I wrote, or is it

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/26/2015 07:06 PM, Reindl Harald wrote: > people needing handholding - bah See, your problem is more a limited mindset / perspective problem. From your attitude, you believe it's demeaning to use the proper tool for the job, taking it as a point of pride that you have deficient and obsolete

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 07:30 PM, Alex Crawford wrote: > We use it within CoreOS to allow the user to inject dynamic data into the > service. For example, you may have a service like this: > > $ cat etcd.service > [Unit] > Requires=metadata.service > After=metadata.service > > [Service] >

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 19:41 schrieb Manuel Amador (Rudd-O): On 12/23/2015 10:40 PM, Reindl Harald wrote: why should i change anything in *my* configuartion *because* you don't like it? Nobody is forcing you to change anything from your configuration Johann would if he had the power to do so

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 10:29 PM, Marc Haber wrote: > The problem is that a minoriy of concepts and the attitude of the > makers make working with systemd a constant source of increased blood > pressure and a strong urge to break something expensive just to get > rid of the aggression. For that, there's

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 09:41 PM, Marc Haber wrote: > This is exactly why systemd is the top one most hated piece of open > source software. We are not here to be educated about the one and only > right way of doing things. Actually, you hate systemd because you don't like that systemd forces you to learn

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/10/2015 03:20 PM, Reindl Harald wrote: > > Apache: > > Include "conf/local/testserver.conf" > > > 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 This

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 19:49 schrieb Manuel Amador (Rudd-O): Meanwhile, we're still in 1980 dicking around with EnvironmentFiles and FlagFiles and such bullshit boy just don't use it if you don't like it nobody is forcing you to use anything - on the other hand some systemd people trying to

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/26/2015 07:12 PM, Reindl Harald wrote: > you said "reload would be possible again" Let me spell that sentence out in context: If you stopped using EnvironmentFile and starting actually assembling proper configurations using a configuration management tool, then the command "systemctl

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 08:18 PM, Reindl Harald wrote: > and what's the difference between a config file or "EnvironmentFile" > besides you like the one for whatever reason more while both are > config files? It has already been explained that certain operations will not cause the EnvironmentFile contents

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 10:40 PM, Reindl Harald wrote: > why should i change anything in *my* configuartion *because* you don't > like it? Nobody is forcing you to change anything from your configuration. Even though environment files are shit for configuration (the reasoning of which has already been

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 19:34 schrieb Manuel Amador (Rudd-O): On 12/21/2015 09:41 PM, Marc Haber wrote: This is exactly why systemd is the top one most hated piece of open source software. We are not here to be educated about the one and only right way of doing things. Actually, you hate systemd

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/11/2015 02:59 PM, Reindl Harald wrote: > and that's exactly what i don't want to do for damned good reasons > > * in the past i started httpd with type=forking > * it was just "/usr/sbin/httpd $OPTIONS" > * switch to "Type=simple" was change the untit in our own > maintained rpm-package

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:02 schrieb Manuel Amador (Rudd-O): On 12/16/2015 09:47 AM, Reindl Harald wrote: "normal people" - what's wrong with you? Us "normal people" use configuration management systems to properly do what you do with ugly hacks. It's 2015. cfengine is not the only game in

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/26/2015 06:58 PM, Reindl Harald wrote: > > > Am 26.12.2015 um 19:52 schrieb Manuel Amador (Rudd-O): > > i am capable to write my configs by hand withoput babysitting by > Puppet or something else What a macho man! Guess what: those of us who use configuration systems also write configs by

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:04 schrieb Manuel Amador (Rudd-O): On 12/16/2015 09:47 AM, Reindl Harald wrote: because i know how to configure servers and don't need handholding tools since i develop my own admin backends for many years and services helping on repeatly needed taks but don't chain me to

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/20/2015 01:30 PM, Marc Haber wrote: > > How would I do the equivalent of systemctl edit with a declarative > configuration management tool like puppet? systemctl edit on a host copy the file to your puppet server (ugh, don't use puppet, use ansible) deploy file across hosts -- Rudd-O

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:19 schrieb Manuel Amador (Rudd-O): On 12/26/2015 07:06 PM, Reindl Harald wrote: people needing handholding - bah See, your problem is more a limited mindset / perspective problem. From your attitude, you believe it's demeaning to use the proper tool for the job, taking

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 07:48 PM, Lennart Poettering wrote: > I see no reason why systemd should be involved with this. Just make > etcd a proper daemon, and read its config data directly, rather then > serializing it into the command line. > > Lennart Reading from environment / flagfiles / command line is

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 19:52 schrieb Manuel Amador (Rudd-O): On 12/10/2015 03:20 PM, Reindl Harald wrote: Apache: Include "conf/local/testserver.conf" 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

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:07 schrieb Manuel Amador (Rudd-O): On 12/26/2015 06:58 PM, Reindl Harald wrote: uhm - "EnvironmentFile" don't change often and so reload is possible all the time I never said you couldn't reload. I said that reload would not enact your environment file changes. Are

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/26/2015 07:28 PM, Reindl Harald wrote: > > my infrastructure is most likely better managed than anyone leses So says the person with a limited perspective and a refusal to learn modern tools and processes. > > you are not in the position to give orders Did you just forget that it was YOU

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 26.12.2015 um 20:39 schrieb Manuel Amador (Rudd-O): On 12/26/2015 07:28 PM, Reindl Harald wrote: impressive what a arrgoant asshole you are while talking about "Arrogant" is the guy who refuses to accept new ways of doing things, because he thinks that the way he does things is perfect

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 10:32, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.12.2015 um 07:01 schrieb Jóhann B. Guðmundsson: > >On 12/23/2015 12:43 AM, Lennart Poettering wrote: > >>Just to clarify that. I think EnvironmentFile= was a mistake, and I > >>explained why. But then again, I am

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 02:44, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 23.12.2015 um 01:24 schrieb Lennart Poettering: > >On Thu, 10.12.15 16:20, Reindl Harald (h.rei...@thelounge.net) wrote: > >> > >>Am 10.12.2015 um 15:46 schrieb Jóhann B. Guðmundsson: > >>>If you are unaware of any

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > On 12/23/2015 12:43 AM, Lennart Poettering wrote: > >Just to clarify that. I think EnvironmentFile= was a mistake, and I > >explained why. But then again, I am not planning to remove it, and I > >never suggested

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23, Lennart Poettering wrote: > On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > What usescases do you see for it's existence. > > Well, the usecase that this is what's out there right now, and we have > to stay compatible. It's not precisely an exotic feature,

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23, Jóhann B. Guðmundsson wrote: > The usual underlying cause of usage of Environment or EnvironmentFile in > type units is more or less always due to the fact that the > daemon/service cannot read configuration file on startup thus the answer > is you would use a daemon that was written

Re: [systemd-devel] Query regarding "EnvironmentFile"

24.12.2015 03:48, Alex Crawford пишет: > On 12/23, Jóhann B. Guðmundsson wrote: >> The usual underlying cause of usage of Environment or EnvironmentFile in >> type units is more or less always due to the fact that the >> daemon/service cannot read configuration file on startup thus the answer

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 21:12 schrieb Jóhann B. Guðmundsson: On 12/23/2015 07:30 PM, Alex Crawford wrote: I like this model and I'm not sure how I would solve this if EnvironmentFile didn't exist. The usual underlying cause of usage of Environment or EnvironmentFile in type units is more or less

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 23:08 schrieb Jóhann B. Guðmundsson: On 12/23/2015 08:18 PM, Reindl Harald wrote: Am 23.12.2015 um 21:12 schrieb Jóhann B. Guðmundsson: On 12/23/2015 07:30 PM, Alex Crawford wrote: I like this model and I'm not sure how I would solve this if EnvironmentFile didn't

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 23.12.15 11:30, Alex Crawford (alex.crawf...@coreos.com) wrote: > On 12/23, Lennart Poettering wrote: > > On Wed, 23.12.15 06:01, Jóhann B. Guðmundsson (johan...@gmail.com) wrote: > > > What usescases do you see for it's existence. > > > > Well, the usecase that this is what's out there

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 07:48 PM, Lennart Poettering wrote: I see no reason why systemd should be involved with this. Just make etcd a proper daemon, and read its config data directly, rather then serializing it into the command line. In sys v initscript it started out as variable options, placed on

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 07:01 schrieb Jóhann B. Guðmundsson: On 12/23/2015 12:43 AM, Lennart Poettering wrote: Just to clarify that. I think EnvironmentFile= was a mistake, and I explained why. But then again, I am not planning to remove it, and I never suggested that. What usescases do you see

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Mon, 21.12.15 22:41, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > On Mon, Dec 21, 2015 at 10:18:05PM +0100, Kai Krakow wrote: > > Thus: Please maintainers and developers, remove it. Do not let Lennart > > remove this useful option to force others into removing your shitty > > cruft. >

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Fri, 18.12.15 17:00, Michael Biebl (mbi...@gmail.com) wrote: > I do think that overriding the complete ExecStart= line is usually > suboptimal and not what you want if you just want to pass additional > options to the daemon. > > Maybe a good middle ground / recommendation for such daemons

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Thu, 10.12.15 16:20, Reindl Harald (h.rei...@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 > >

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 01:32 schrieb Lennart Poettering: On Fri, 18.12.15 17:00, Michael Biebl (mbi...@gmail.com) wrote: I do think that overriding the complete ExecStart= line is usually suboptimal and not what you want if you just want to pass additional options to the daemon. Maybe a good

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Sun, 20.12.15 14:30, Marc Haber (mh+systemd-de...@zugschlus.de) wrote: > On Fri, Dec 18, 2015 at 05:00:32PM +0100, Michael Biebl wrote: > > and then tell admin to use systemctl edit > > [Unit] > > Environment=OPTS=-baz > > How would I do the equivalent of systemctl edit with a declarative >

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Tue, 22.12.15 11:27, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 22.12.2015 um 00:16 schrieb Kai Krakow: > >Back to concepts: I'm always trying to find my way through the new > >ideas, trying to understand it instead of denying it, then re-apply my > >workflow. If it doesn't fit,

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 23.12.2015 um 01:24 schrieb Lennart Poettering: On Thu, 10.12.15 16:20, Reindl Harald (h.rei...@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

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 22.12.2015 um 00:16 schrieb Kai Krakow: Back to concepts: I'm always trying to find my way through the new ideas, trying to understand it instead of denying it, then re-apply my workflow. If it doesn't fit, throw either that away, or the software. Probably one of many reasons why I chose

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 04:36 PM, Michael Biebl wrote: 2015-12-21 17:30 GMT+01:00 Jóhann B. Guðmundsson : It's an added work to add the environmental line to begin with and it's an That would be done once, by upstream ideally. The work would be negligible. Still an added work

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/23/2015 12:43 AM, Lennart Poettering wrote: Just to clarify that. I think EnvironmentFile= was a mistake, and I explained why. But then again, I am not planning to remove it, and I never suggested that. What usescases do you see for it's existence. FYI the longer you take fixing your

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am Thu, 10 Dec 2015 01:08:34 +0100 schrieb Reindl Harald : > Am 09.12.2015 um 20:46 schrieb Lennart Poettering: > > I probably should never have added EnvironmentFile= in the first > > place. Packagers misunderstand that unit files are subject to admin > > configuration

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am Mon, 21 Dec 2015 22:41:04 +0100 schrieb Marc Haber : > On Mon, Dec 21, 2015 at 10:18:05PM +0100, Kai Krakow wrote: > > Thus: Please maintainers and developers, remove it. Do not let > > Lennart remove this useful option to force others into removing > > your

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Mon, Dec 21, 2015 at 11:14:43PM +0100, Kai Krakow wrote: > I cannot see anything here in the thread which would disallow continue > using non-systemd installations. The problem is that many concepts of systemd are really nice. Once wants to have things like that. The problem is that a minoriy

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Mon, Dec 21, 2015 at 10:18:05PM +0100, Kai Krakow wrote: > Thus: Please maintainers and developers, remove it. Do not let Lennart > remove this useful option to force others into removing your shitty > cruft. This is exactly why systemd is the top one most hated piece of open source software.

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am Mon, 21 Dec 2015 23:29:57 +0100 schrieb Marc Haber : > On Mon, Dec 21, 2015 at 11:14:43PM +0100, Kai Krakow wrote: > > I cannot see anything here in the thread which would disallow > > continue using non-systemd installations. > > The problem is that many

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 01:30 PM, Reindl Harald wrote: ExecStart=/path/to/daemon FOO would cut you from distro-changes in other params and explained abvoe sooner or later lead in failing and could even be security relevant depending on new options or removed options in the distro-unit You do

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 21.12.2015 um 15:08 schrieb Jóhann B. Guðmundsson: On 12/21/2015 01:30 PM, Reindl Harald wrote: ExecStart=/path/to/daemon FOO would cut you from distro-changes in other params and explained abvoe sooner or later lead in failing and could even be security relevant depending on new options

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 21.12.2015 um 14:23 schrieb Jóhann B. Guðmundsson: On 12/21/2015 01:00 PM, Reindl Harald wrote: Am 21.12.2015 um 12:40 schrieb Jóhann B. Guðmundsson: ExecStart=/usr/sbin/foobard $OPTS and then tell admin to use systemctl edit [Unit] Environment=OPTS=-baz bonus points if we could

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/18/2015 04:00 PM, Michael Biebl wrote: 2015-12-09 20:46 GMT+01:00 Lennart Poettering : On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote: Hi, I have created a systemd.unit(nfs-ganesha.service) file as below : [Unit]

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 21.12.2015 um 12:40 schrieb Jóhann B. Guðmundsson: ExecStart=/usr/sbin/foobard $OPTS and then tell admin to use systemctl edit [Unit] Environment=OPTS=-baz bonus points if we could standardise the $OPTS var name across daemons. Then distros like Fedora could do a one-time migration of

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 01:00 PM, Reindl Harald wrote: Am 21.12.2015 um 12:40 schrieb Jóhann B. Guðmundsson: ExecStart=/usr/sbin/foobard $OPTS and then tell admin to use systemctl edit [Unit] Environment=OPTS=-baz bonus points if we could standardise the $OPTS var name across daemons. Then distros

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-21 17:30 GMT+01:00 Jóhann B. Guðmundsson : > It's an added work to add the environmental line to begin with and it's an That would be done once, by upstream ideally. The work would be negligible. > equal amount of work for administrators to change the environmental

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 04:02 PM, Michael Biebl wrote: 2015-12-21 17:00 GMT+01:00 Jóhann B. Guðmundsson : No what's obvious is it does not add any value not et all Well, I can reiterate the points, but I suggest you just read this thread again. and not all daemons and service

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-21 14:23 GMT+01:00 Jóhann B. Guðmundsson : > What he proposed is redundant and adds an extra line to the unit file and in > addition requires some distro's acceptance that upstream needs to be aware > of when it creates the unit for it's daemon/service. > > His proposal

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 02:15 PM, Reindl Harald wrote: and since you say this what is your business for taking "EnvironmentFile" away from administrators area - my config, take your hands from it instead propose to break it - nobody cares if you would something do in a different way as long you are

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/21/2015 03:17 PM, Michael Biebl wrote: The benefit of that instead of having to override the complete ExecStart line should be obvious and has already be mentioned in this very thread. No what's obvious is it does not add any value not et all and not all daemons and service support

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-21 17:00 GMT+01:00 Jóhann B. Guðmundsson : > No what's obvious is it does not add any value not et all Well, I can reiterate the points, but I suggest you just read this thread again. and not all > daemons and service support additional environmental options added to

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Sun, Dec 20, 2015 at 02:30:30PM +0100, Marc Haber wrote: > On Fri, Dec 18, 2015 at 05:00:32PM +0100, Michael Biebl wrote: > > and then tell admin to use systemctl edit > > [Unit] > > Environment=OPTS=-baz > > How would I do the equivalent of systemctl edit with a declarative > configuration

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Sun, Dec 20, 2015 at 02:34:15PM +0100, Tomasz Torcz wrote: > On Sun, Dec 20, 2015 at 02:30:30PM +0100, Marc Haber wrote: > > On Fri, Dec 18, 2015 at 05:00:32PM +0100, Michael Biebl wrote: > > > and then tell admin to use systemctl edit > > > [Unit] > > > Environment=OPTS=-baz > > > > How would

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Fri, Dec 18, 2015 at 05:00:32PM +0100, Michael Biebl wrote: > and then tell admin to use systemctl edit > [Unit] > Environment=OPTS=-baz How would I do the equivalent of systemctl edit with a declarative configuration management tool like puppet? Greetings Marc --

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Tue, Dec 15, 2015 at 05:59:11PM +, Simon Peeters wrote: > Why not do like normal people and use configmanagement to put the > right apache config on the right host? > This whole "-D testserver" and "" looks like an > ugly workaround for a lacking configmanagment system. And what is your

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Fri, Dec 11, 2015 at 03:59:54PM +0100, Reindl Harald wrote: > EnvironmentFile is a great way to make units flexible with sane > defaults and i am *not* talking about upstream or distributions here > > so taking away that option gains you nothing but breaks things for > no valid reason - it

Re: [systemd-devel] Query regarding "EnvironmentFile"

20.12.2015 16:47, Marc Haber пишет: > On Sun, Dec 20, 2015 at 02:34:15PM +0100, Tomasz Torcz wrote: >> On Sun, Dec 20, 2015 at 02:30:30PM +0100, Marc Haber wrote: >>> On Fri, Dec 18, 2015 at 05:00:32PM +0100, Michael Biebl wrote: and then tell admin to use systemctl edit [Unit]

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-09 20:46 GMT+01:00 Lennart Poettering : > On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote: > >> Hi, >> >> I have created a systemd.unit(nfs-ganesha.service) file as below : >> >> [Unit] >> >> After=nfs-ganesha-config.service >>

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-16 9:47 GMT+00:00 Reindl Harald : > > > Am 15.12.2015 um 18:59 schrieb Simon Peeters: >> >> 2015-12-10 15:20 GMT+00:00 Reindl Harald : >>> >>> >>> Am 10.12.2015 um 15:46 schrieb Jóhann B. Guðmundsson: If you are unaware of any

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 15.12.2015 um 18:59 schrieb Simon Peeters: 2015-12-10 15:20 GMT+00:00 Reindl Harald : 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

Re: [systemd-devel] Query regarding "EnvironmentFile"

2015-12-10 15:20 GMT+00:00 Reindl Harald : > > 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@testserver:~]$

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/11/2015 03:56 AM, Andrei Borzenkov wrote: 10.12.2015 18:44, 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: Care to show example how it should be done from your point of view? So that they can actully be

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 11.12.2015 um 15:45 schrieb Jóhann B. Guðmundsson: On 12/11/2015 03:56 AM, Andrei Borzenkov wrote: 10.12.2015 18:44, 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: Care to show example how it should be

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Thu, 10.12.15 01:08, Reindl Harald (h.rei...@thelounge.net) wrote: > > > Am 09.12.2015 um 20:46 schrieb Lennart Poettering: > >I probably should never have added EnvironmentFile= in the first > >place. Packagers misunderstand that unit files are subject to admin > >configuration and should

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 10.12.2015 um 11:15 schrieb Lennart Poettering: On Thu, 10.12.15 01:08, Reindl Harald (h.rei...@thelounge.net) wrote: Am 09.12.2015 um 20:46 schrieb Lennart Poettering: I probably should never have added EnvironmentFile= in the first place. Packagers misunderstand that unit files are

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 09/12/15 19:46, Lennart Poettering wrote: > Also /etc/sysconfig is a Redhatism > that should really go away, the whole concept is flawed. This is by no means limited to Red Hat derivatives: /etc/default is a Debianism which is basically the same as /etc/sysconfig. I think Red Hat and Debian

Re: [systemd-devel] Query regarding "EnvironmentFile"

10.12.2015 18:44, 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 it >> >> EnvironmentFile=-/etc/sysconfig/httpd >> ExecStart=/usr/sbin/httpd $OPTIONS -D

Re: [systemd-devel] Query regarding "EnvironmentFile"

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 it EnvironmentFile=-/etc/sysconfig/httpd ExecStart=/usr/sbin/httpd $OPTIONS -D FOREGROUND

Re: [systemd-devel] Query regarding "EnvironmentFile"

> only wanted to maintain a single unit file but cross > distribution compatibility and the importance of it > is something you dont seem to be capable of grasping > since the only use cases that matters is the one that > is specific and relevant to you" no, but you don't grasp that options for

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/09/2015 07:46 PM, Lennart Poettering wrote: I probably should never have added EnvironmentFile= in the first place. Packagers misunderstand that unit files are subject to admin configuration and should be treated as such, and that spliting out configuration of unit files into separate

Re: [systemd-devel] Query regarding "EnvironmentFile"

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@testserver:~]$ cat /etc/sysconfig/httpd OPTIONS="-D testserver" Apache: Include

Re: [systemd-devel] Query regarding "EnvironmentFile"

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 it EnvironmentFile=-/etc/sysconfig/httpd ExecStart=/usr/sbin/httpd $OPTIONS -D FOREGROUND [root@testserver:~]$ cat /etc/sysconfig/httpd

Re: [systemd-devel] Query regarding "EnvironmentFile"

Am 09.12.2015 um 20:46 schrieb Lennart Poettering: I probably should never have added EnvironmentFile= in the first place. Packagers misunderstand that unit files are subject to admin configuration and should be treated as such, and that spliting out configuration of unit files into separate

Re: [systemd-devel] Query regarding "EnvironmentFile"

On 12/10/2015 01:16 AM, Lennart Poettering wrote: On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote: Hi, I have created a systemd.unit(nfs-ganesha.service) file as below : [Unit] After=nfs-ganesha-config.service Requires=nfs-ganesha-config.service [Service]

Re: [systemd-devel] Query regarding "EnvironmentFile"

10.12.2015 03:08, Reindl Harald пишет: > > > Am 09.12.2015 um 20:46 schrieb Lennart Poettering: >> I probably should never have added EnvironmentFile= in the first >> place. Packagers misunderstand that unit files are subject to admin >> configuration and should be treated as such, and that

Re: [systemd-devel] Query regarding "EnvironmentFile"

On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote: > Hi, > > I have created a systemd.unit(nfs-ganesha.service) file as below : > > [Unit] > > After=nfs-ganesha-config.service > Requires=nfs-ganesha-config.service > > > [Service] > EnvironmentFile=-/run/sysconfig/ganesha >