Re: [systemd-devel] Antw: Re: Antw: [EXT] Re: Q: journal logging and "{xyz}"

On 27/12/2021 12:25, Ulrich Windl wrote: Wols Lists schrieb am 27.12.2021 um 13:18 in Nachricht <8802ee4d-230d-8013-553d-8615515ce...@youngman.org.uk>: On 27/12/2021 12:09, Ulrich Windl wrote: Well, but why write "Failed to kill unit \x7b__SERVICE__\x7d.service" when "u

Re: [systemd-devel] Antw: [EXT] Re: the need for a discoverable sub-volumes specification

On 28/12/2021 19:02, Chris Murphy wrote: Yeah how to handle /boot gives me headaches. We have a kind of rollback, the possibility of choosing among kernels. But which kernels are bootable depends on the /usr its paired with. We need a mechanism to match /boot and /usr together, so that the user

Re: [systemd-devel] Antw: [EXT] Re: Q: journal logging and "{xyz}"

On 27/12/2021 12:09, Ulrich Windl wrote: Well, but why write "Failed to kill unit \x7b__SERVICE__\x7d.service" when "unit {__SERVICE__} has an invalid name" (the message I'd suggest)? I mean: I see no problem_outputting_ the original service name, especially when it's considered to be an

Re: [systemd-devel] Service activation

On 13/02/2022 09:54, Mantas Mikulėnas wrote: On Sun, Feb 13, 2022 at 2:03 AM Wol > wrote: More fun getting things to work ... :-) So I've got a service, scarletdme.service, which fires up my db backend for running interactively. However, I also need

Re: [systemd-devel] Service activation

On 13/02/2022 15:46, Mantas Mikulėnas wrote: On Sun, Feb 13, 2022 at 1:09 PM Wols Lists <mailto:antli...@youngman.org.uk>> wrote: On 13/02/2022 09:54, Mantas Mikulėnas wrote: > On Sun, Feb 13, 2022 at 2:03 AM Wol mailto:antli...@youngman.org.uk> > <mailto:ant

Re: [systemd-devel] Antw: [EXT] Re: [systemd‑devel] How to find out the processes systemd‑shutdown is waiting for?

On 04/03/2022 07:20, Ulrich Windl wrote: Docker traditionally has not followed any of our documented ways to You are implying that "our documented ways" is a definitive standard? cgroups is a THIRD PARTY to both Docker and systemd. If Docker doesn't document what they're doing, how is

Re: [systemd-devel] Antw: [EXT] Service activation

On 14/02/2022 08:27, Ulrich Windl wrote: And once I've got all that sorted, I'm betting I'm going to have grief getting it to work properly, so while it's not much to do with systemd, is there any way I can get systemd to log all traffic back and forth so I can debug it? Maybe understandable

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 07/02/2022 14:06, Mantas Mikulėnas wrote: On Mon, Feb 7, 2022 at 2:54 PM Wols Lists <mailto:antli...@youngman.org.uk>> 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

[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] Have I got circular dependencies?

On 23/01/2022 19:44, Andrei Borzenkov wrote: Where dependency to /home comes from? It is not in your unit file. If it thinks my unit depends on /home, that's wrong. /home comes from fstab, and the partition is not available until AFTER my service has run. Home is on an lv, which is on raid,

[systemd-devel] Have I got circular dependencies?

This is probably a classic "need a clue" problem ... my system has suddenly stopped booting properly, and I guess it's a problem with my custom systemd service. Basically, I've configured my raid device on top of dm-integrity, so that needs to be set up before my /home becomes visible. I've

Re: [systemd-devel] Have I got circular dependencies?

On 24/01/2022 11:08, Kevin P. Fleming wrote: According to 'man systemd.unit' it goes in the '[Unit]' section, like all other dependency statements. Thank you very much. The usual problem of "where's the docu I'm looking for?" :-) Cheers, Wol On Sun, Jan 23, 2022 at 3:15 PM

Re: [systemd-devel] Antw: [EXT] Dropping split-usr/unmerged-usr support

On 06/04/2022 10:34, Luca Boccassi wrote: Symlinking /sbin or /usr/sbin binaries to /usr is also a bad concept IMHO. It seems systemd is the new Microsoft ("We know what is good for you; just accept it!");-) Well, I saw a link to WHY we have /bin, /usr/bin, /sbin etc. Interesting read ...

Re: [systemd-devel] Samba Config Reload

On 09/04/2022 09:00, Yolo von BNANA wrote: Can you please explain this in more Detail? What does this mean: " "systemctl reload" will basically return immediately without the reload being complete"? And what is an Example for an synchronous command for ExecReload= Do you understand the

Re: [systemd-devel] Antw: Re: Antw: [EXT] Re: Q: Start network in chroot?

On 14/06/2022 06:57, Ulrich Windl wrote: So you're not running an init system but you want the (not-running) init system to run something for you? I don't understand: The rescue system I'm using (SLES 14 SP3) uses systemd, and the system that woon't boo is also using systemd (SLES15 SP3).

Re: [systemd-devel] Feedback sought: can we drop cgroupv1 support soon?

On 22/07/2022 11:15, Lennart Poettering wrote: I guess that would mean holding on to cgroup1 support until EOY 2023 or thereabout? That does sound OK to me. We can mark it deprecated before though, i.e. generate warnings, and remove it from docs, as long as the actual code stays around until

Re: [systemd-devel] Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora

On 27/04/2022 14:53, Lennart Poettering wrote: I think we systematically disagree on one point here: I am pretty sure picking a boot loader is genuinely someting a distro should be doing, and not the admin really. I mean, yes, I personally of course switched away from Fedora's default choice of

Re: [systemd-devel] Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora

On 28/04/2022 11:30, Ulrich Windl wrote: my educated guess is that your distro is providing some emergency kernel for you that comes with a minimized initrd? If that's the case it's purely the decision of your distro what to put in there and what not. So are there any distros that have

Re: [systemd-devel] Antw: [EXT] [systemd‑devel] systemd‑tmpfiles: behavior of ‑‑clean

On 31/08/2022 07:16, Ulrich Windl wrote: 'tomcat.<>' with other associated files (or directories below this). I think with the guideline "clean up your own dirt" there wouldn't be so much need for external cleanup if the applications would do a better job. The application always knows

Re: [systemd-devel] Antw: [EXT] Re: Support for unmerged-usr systems will be REMOVED in the second half of 2023

On 07/11/2022 07:07, Ulrich Windl wrote: o, that is unrelated. This is about the ancient notion (that no initrd tools support anymore) that you can boot userspace with /bin /lib /sbin and no /usr, with the latter being set up late at boot. This is what is no longer going to be supported. ..by