[systemd-devel] Environment and additional command line options

[arnaud gaboury]

On Mon, Feb 1, 2016 at 10:48 AM, Mantas Mikulėnas <grawity at gmail.com> wrote:
> On Mon, Feb 1, 2016 at 11:37 AM, arnaud gaboury <arnaud.gaboury at gmail.com>
> wrote:
>>
>> $ systemctl --version
>> systemd 22
>
>
> v22 was released five years ago, are you sure?
222, sorry for the typo


>
>>
>>  One way to pass additional options is to add one of these lines in
>> the [Service] part of the unit file:
>>
>> ------------
>> Environment=ONE='one'
>> EnvironmentFile=/path/to
>> -------------------
>>
>> If I am right, there is another possible mechanism since recent
>> versions by adding a configuration file somewhere in /etc/systemd, but
>> I can't remember how exactly do it. I think the way is to edit a
>> MyService.conf and place it in /etc/systemd/system.conf.d. Am I right?
>>  /etc/systemd/system/MyService.service.conf directory is to add
>> override vendor settings. I
>
>
> Search systemd.unit(5) for "drop-in". There is no special syntax, the
> additional .conf files act exactly like a part of the main unit file.

Yes I have seen it. This mechanism uses
/etc/systemd/system/MyService.service.conf directory to store a
locale.conf. But what about using /etc/systemd/systemd.conf.d
directory instead ?
>
> --
> Mantas Mikulėnas <grawity at gmail.com>



-- 

google.com/+arnaudgabourygabx