[systemd-devel] Antw: Re: Antw: [EXT] [systemd‑devel] Why is using fstab the preferred approach according to systemd.mount man page?

>>> Thomas HUMMEL schrieb am 07.02.2022 um 18:36 in Nachricht <3aa03772-1981-eea4-ecd2-c50b9c0d0...@pasteur.fr>: > > On 10/01/2022 21:50, Zbigniew Jędrzejewski-Szmek wrote: > >> Pretty much. There isn't any big benefit to using mount units (since the >> fstab syntax supports all the important

Re: [systemd-devel] Odd behaviour on boot

On Mon, Feb 7, 2022, 22:06 Tomasz Torcz wrote: > On Mon, Feb 07, 2022 at 07:28:46PM +, Wols Lists wrote: > > On 07/02/2022 17:55, Mantas Mikulėnas wrote: > > > Basically you have *a lot* of service daemons getting killed – some of > > > them restart cleanly, others not – and it looks a bit

Re: [systemd-devel] Odd behaviour on boot

On Mon, Feb 07, 2022 at 07:28:46PM +, Wols Lists wrote: > On 07/02/2022 17:55, Mantas Mikulėnas wrote: > > Basically you have *a lot* of service daemons getting killed – some of > > them restart cleanly, others not – and it looks a bit like scarletdme is > > the one doing it. It even looks

Re: [systemd-devel] Odd behaviour on boot

On 07/02/2022 17:55, Mantas Mikulėnas wrote: Basically you have *a lot* of service daemons getting killed – some of them restart cleanly, others not – and it looks a bit like scarletdme is the one doing it. It even looks like it ended up killing itself, too. Thank you very much. I think that

Re: [systemd-devel] Odd behaviour on boot

On Mon, Feb 7, 2022, 19:43 Wols Lists wrote: > On 07/02/2022 14:06, Mantas Mikulėnas wrote: > > On Mon, Feb 7, 2022 at 2:54 PM Wols Lists > > wrote: > > > > Bear in mind I did have a malformed scarletdme.service file, it was > > missing "Type=forking",

Re: [systemd-devel] Odd behaviour on boot

On 07/02/2022 14:06, Mantas Mikulėnas wrote: On Mon, Feb 7, 2022 at 2:54 PM Wols Lists > wrote: Bear in mind I did have a malformed scarletdme.service file, it was missing "Type=forking", but it shouldn't be bringing down unrelated services, should

Re: [systemd-devel] Antw: [EXT] [systemd‑devel] Why is using fstab the preferred approach according to systemd.mount man page?

On 10/01/2022 21:50, Zbigniew Jędrzejewski-Szmek wrote: Pretty much. There isn't any big benefit to using mount units (since the fstab syntax supports all the important use cases), and people are familiar with fstab. More tools support it too. Hello, well although I'm not currently using

Re: [systemd-devel] Failed to add PIDs to scope's control group: No such process

On 03.02.2022 18:39, Gena Makhomed wrote: Periodically I see in /var/log/messages error message about Failed to add PIDs to scope's control group: No such process Failed with result 'resources'. How I can resolve or workaround this error? # rpm -q systemd systemd-239-51.el8_5.3.x86_64 # cat

Re: [systemd-devel] Odd behaviour on boot

On Mon, Feb 7, 2022 at 2:54 PM Wols Lists wrote: > Bear in mind I did have a malformed scarletdme.service file, it was > missing "Type=forking", but it shouldn't be bringing down unrelated > services, should it? > > This is the output from dovecot, which clearly failed to start on boot... > >

[systemd-devel] Odd behaviour on boot

Bear in mind I did have a malformed scarletdme.service file, it was missing "Type=forking", but it shouldn't be bringing down unrelated services, should it? This is the output from dovecot, which clearly failed to start on boot... thewolery /dev # systemctl status dovecot × dovecot.service -

Re: [systemd-devel] Strange behavior of socket activation units

On Mo, 07.02.22 09:01, Tuukka Pasanen (pasanen.tuu...@gmail.com) wrote: > Hello, > I have encountered this kind of problem. This particularly is MariaDB 10.6 > installation to Debian. > Nearly every application that is restarted/started dies on: > > > Failed to get properties: Unit name