03.07.2020 12:09, Thomas HUMMEL пишет:
>
>
> On 02/07/2020 20:48, Andrei Borzenkov wrote:
>
>
>> Once again - dependencies in systemd are between jobs, not between units.
>
> Ok. I may have missed some docs but I've read several man sections
> (likesystemd.service(5) and so on) as well as some
On 02/07/2020 20:48, Andrei Borzenkov wrote:
Once again - dependencies in systemd are between jobs, not between units.
Ok. I may have missed some docs but I've read several man sections
(likesystemd.service(5) and so on) as well as some 0pointer blog
articles) and I did experiment a lot.
02.07.2020 21:28, Thomas HUMMEL пишет:
>
>
> On 02/07/2020 19:00, Andrei Borzenkov wrote:
>
>> After=syslog.socket will exist only if rsyslog.service is aliased to
>> syslog.service and your problem was when you removed this alias.
>
> Correct (I did miss this simple thing) !
>
>
>> On boot a
On 02/07/2020 19:00, Andrei Borzenkov wrote:
After=syslog.socket will exist only if rsyslog.service is aliased to
syslog.service and your problem was when you removed this alias.
Correct (I did miss this simple thing) !
On boot activation of syslog.socket happens much earlier than activa
02.07.2020 18:57, Thomas HUMMEL пишет:
>
>
> On 02/07/2020 16:44, Andrei Borzenkov wrote:
>
>> This is common misunderstanding. Dependencies are between jobs, not
>> between units. Requires means systemd will submit additional job for
>> dependent unit - nothing more nothing less. Unless systemd
On 02/07/2020 16:44, Andrei Borzenkov wrote:
This is common misunderstanding. Dependencies are between jobs, not
between units. Requires means systemd will submit additional job for
dependent unit - nothing more nothing less. Unless systemd is also told
to wait for result of this additional j
02.07.2020 16:09, Thomas HUMMEL пишет:
>
> [Unit]
> Requires=syslog.socket
>
> [Install]
> ;Alias=syslog.service
>
...
>
> # systemctl start rsyslog
> A dependency job for rsyslog.service failed. See 'journalctl -xe' for
> details.
>
> BUT rsyslog service (and daemon) are actually running:
>
Am 02.07.20 um 15:09 schrieb Thomas HUMMEL:
> On CentOS Linux release 8.1.1911 (Core) x86_64 running systemd-239 and
> rsyslog-8.37.0 I'm experiencing a sometime strange (to me) activation of
> rsyslog.service when I would expect it to fail for a dependency reason.
>
> Note : I know how to make
Hello,
On CentOS Linux release 8.1.1911 (Core) x86_64 running systemd-239 and
rsyslog-8.37.0 I'm experiencing a sometime strange (to me) activation of
rsyslog.service when I would expect it to fail for a dependency reason.
Note : I know how to make rsyslog and systemd coexist and I did
succe
