Re: [systemd-devel] [Install] section of symlinked unit file ignored if drop-in file is used

I'm using v237, so that makes sense. Thanks for looking into this! -John On Sun, May 27, 2018 at 6:50 AM, 林自均 wrote: > Hi John, > > I can reproduced your problem on systemd v236 to v238, but not v235. I think > it's because from v236 to v238 contains the commit in >

Re: [systemd-devel] [Install] section of symlinked unit file ignored if drop-in file is used

Hi John, I can reproduced your problem on systemd v236 to v238, but not v235. I think it's because from v236 to v238 contains the commit in https://github.com/systemd/systemd/pull/7158. However, it seems that the commit "d04a93864d" in the git repo fixes the issue. Therefore, you can expect that

Re: [systemd-devel] [Install] section of symlinked unit file ignored if drop-in file is used

Hi John, I'm not sure whether this issue is because of https://github.com/systemd/systemd/pull/7158 or not. I will figure it out. Thanks. John Lin John Gallagher 於 2018年5月24日 週四 上午8:07寫道： > If I have a unit file for a service that lives off the unit file > search

[systemd-devel] [Install] section of symlinked unit file ignored if drop-in file is used

If I have a unit file for a service that lives off the unit file search path, I can link it, and then enable it using the service name instead of the full path of the unit file: $ cat foo.service [Service] Type=simple ExecStart=/bin/sleep 1 [Install] WantedBy=multi-user.target $ sudo