Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-30 Thread Michael Biebl
Am 26.04.19 um 03:56 schrieb Norbert Preining: > Hi > >> The man pages say that %h and %u are resolved to the root user if you >> are using the system instance (PID 1). >> That is consistent with the behaviour you are getting. >> If I missed a part which mentions the contrary, could you quote the

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Norbert Preining
Hi > The man pages say that %h and %u are resolved to the root user if you > are using the system instance (PID 1). > That is consistent with the behaviour you are getting. > If I missed a part which mentions the contrary, could you quote the > relevant bits from the documentation, so it can be

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Michael Biebl
Am 25.04.19 um 12:24 schrieb Norbert Preining: > Hi > >> From v228 >> https://github.com/systemd/systemd/blob/master/NEWS#L3926 > >> From v209 >> https://github.com/systemd/systemd/blob/master/NEWS#L6855 > > Ok, but the documentation o freedesktop.org and the man pages do not > mention that,

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Norbert Preining
Hi > From v228 > https://github.com/systemd/systemd/blob/master/NEWS#L3926 > From v209 > https://github.com/systemd/systemd/blob/master/NEWS#L6855 Ok, but the documentation o freedesktop.org and the man pages do not mention that, and in fact mention the contrary ... Nobody is supposed to wade

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Michael Biebl
Am 25.04.19 um 11:33 schrieb Michael Biebl: > Am 25.04.19 um 11:28 schrieb Michael Biebl: >> Thanks. So with the above, what you should get is that %h is resolved to >> /root, as you run that service as a system service. Or is %h not >> expanded at all? > > Actually, I think systemd resolves %h

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Michael Biebl
Am 25.04.19 um 11:28 schrieb Michael Biebl: > Thanks. So with the above, what you should get is that %h is resolved to > /root, as you run that service as a system service. Or is %h not > expanded at all? Actually, I think systemd resolves %h for PID 1 to '/'. Would need to double check though.

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Michael Biebl
Am 25.04.19 um 11:09 schrieb Norbert Preining: > Hi Michael, > > On Thu, 25 Apr 2019, Michael Biebl wrote: >> Looks like a duplicate of >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868269 > > Indeed. Interesting that systemd changed the behaviour but it is not > documented ... (well ...

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Norbert Preining
Hi Michael, On Thu, 25 Apr 2019, Michael Biebl wrote: > Looks like a duplicate of > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868269 Indeed. Interesting that systemd changed the behaviour but it is not documented ... (well ... we know). > Can you attach the full .service file please.

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-25 Thread Michael Biebl
Am 25.04.19 um 01:55 schrieb Norbert Preining: > Package: systemd > Version: 241-3 > Severity: important > > Hi > > it seems that the documentation of systemd is incorrect, or incomplete, > as it states that > suffix. In the unit file itself, the instance parameter may be referred > to

Bug#927911: systemd: Does not expand %h identifier in ExecStart

2019-04-24 Thread Norbert Preining
Package: systemd Version: 241-3 Severity: important Hi it seems that the documentation of systemd is incorrect, or incomplete, as it states that suffix. In the unit file itself, the instance parameter may be referred to using "%i" and other specifiers, see below. (man