[systemd-devel] Environment and additional command line options

Mantas Mikulėnas grawity at gmail.com
Mon Feb 1 01:48:36 PST 2016


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?


>  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.

-- 
Mantas Mikulėnas <grawity at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20160201/a68f6cc1/attachment.html>


More information about the systemd-devel mailing list