Re: [systemd-devel] Antw: [EXT] [systemd‑devel] Query degraded state

> On 29 Apr 2022, at 07:06, Ulrich Windl > wrote: > >  >> Barry Scott schrieb am 28.04.2022 um 17:03 in > Nachricht : >> Is there a command I can use to test for the degraded state? >> >> I could parsing the output of systemctl‑failed or >> syetemctl status but was looking for someth

[systemd-devel] Antw: [EXT] Re: Starting transient services securely from other service without root

>>> Vašek Šraier schrieb am 28.04.2022 um 19:47 in Nachricht : > On Thu, 2022-04-28 at 19:53 +0300, Mantas Mikulėnas wrote: ... > > Interesting. The issue also seems to be quite old meaning it's probably > not a problem in practise. ... That's a cool definition! So for any bug just sit and wait

[systemd-devel] Antw: [EXT] [systemd‑devel] Query degraded state

>>> Barry Scott schrieb am 28.04.2022 um 17:03 in Nachricht : > Is there a command I can use to test for the degraded state? > > I could parsing the output of systemctl‑failed or > syetemctl status but was looking for something less fragile. Do you mean "systemctl --state=failed list-units"? >

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

>>> Ian Pilcher schrieb am 28.04.2022 um 16:40 in >>> Nachricht : > On 4/28/22 05:30, Ulrich Windl wrote: >> So are there any distros that have /etc/fstab in initrd? >> Having to start mount units manually is just terrible when a simple "mount >> /var" would do. > > Putting /etc/fstab in the ini

Re: [systemd-devel] Query degraded state

On 28/04/2022 16:15, Alvin Šipraga wrote: Hi, On Thu, Apr 28, 2022 at 04:03:01PM +0100, Barry Scott wrote: Is there a command I can use to test for the degraded state? I could parsing the output of systemctl-failed or syetemctl status but was looking for something less fragile. I think the

Re: [systemd-devel] Starting transient services securely from other service without root

On Thu, Apr 28, 2022 at 6:56 PM Vašek Šraier wrote: > To update the current list of options: > > - PolicyKit > could technically help, but I've discovered that the documentation > explicitly prohibits our potential use-case: > "In particular, applications, [...] must never include any >

Re: [systemd-devel] Query degraded state

Hi, On Thu, Apr 28, 2022 at 04:03:01PM +0100, Barry Scott wrote: > Is there a command I can use to test for the degraded state? > > I could parsing the output of systemctl-failed or > syetemctl status but was looking for something less fragile. I think the correct way to do this programatically

[systemd-devel] Query degraded state

Is there a command I can use to test for the degraded state? I could parsing the output of systemctl-failed or syetemctl status but was looking for something less fragile. Barry

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

On 4/28/22 05:30, Ulrich Windl wrote: So are there any distros that have /etc/fstab in initrd? Having to start mount units manually is just terrible when a simple "mount /var" would do. Putting /etc/fstab in the initrd would mean that it would need to be rebuilt every time that file (or a plugi

Re: [systemd-devel] [systemd‑devel] Antw: [EXT] Re: Q: non‑ASCII in syslog

On Thu, Apr 28, 2022 at 1:26 PM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Lennart Poettering schrieb am 28.04.2022 um > 10:27 > in > Nachricht : > > On Do, 28.04.22 09:32, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) > wrote: > > > >> Actually I wasn't quite sure about th

[systemd-devel] Antw: [EXT] Re: [systemd‑devel] Waiting for all jobs to finish

>>> Lennart Poettering schrieb am 28.04.2022 um 10:47 in Nachricht : > On Mi, 27.04.22 18:29, Barry Scott (barry@barrys‑emacs.org) wrote: > >> I have two target files that I use. >> >> prod.target is used to start up all the production services. >> When I use systemctl start prod.target it blocks

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

>>> Lennart Poettering schrieb am 28.04.2022 um 10:33 in Nachricht : > On Do, 28.04.22 10:25, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> > Well, it sounds backwards to focus on the boot loader UI side of >> > "recovery" so much if you don't even have any reasonably thing you >>

[systemd-devel] Antw: Re: [systemd‑devel] Antw: [EXT] Re: Q: non‑ASCII in syslog

>>> Lennart Poettering schrieb am 28.04.2022 um 10:27 in Nachricht : > On Do, 28.04.22 09:32, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de) wrote: > >> Actually I wasn't quite sure about the default config in SLES12. >> It seems the flow is journald ‑> local rsyslogd ‑> remote syslogd >> >> >

Re: [systemd-devel] Waiting for all jobs to finish

> On 28 Apr 2022, at 09:47, Lennart Poettering wrote: > > On Mi, 27.04.22 18:29, Barry Scott (ba...@barrys-emacs.org > ) wrote: > >> I have two target files that I use. >> >> prod.target is used to start up all the production services. >> When I use systemctl s

[systemd-devel] Antw: Re: [EXT] Re: Q: non-ASCII in syslog

>>> Mantas Mikulenas schrieb am 28.04.2022 um 09:39 in Nachricht : > On Thu, Apr 28, 2022 at 10:32 AM Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> >>> Mantas Mikulenas schrieb am 27.04.2022 um 12:03 in >> Nachricht >> : >> > On Wed, Apr 27, 2022 at 10:09 AM Ulrich Windl < >> >

Re: [systemd-devel] Waiting for all jobs to finish

On Mi, 27.04.22 18:29, Barry Scott (ba...@barrys-emacs.org) wrote: > I have two target files that I use. > > prod.target is used to start up all the production services. > When I use systemctl start prod.target it blocks until all the > services are running. > > I also have prod-upgrade.target tha

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

On Do, 28.04.22 10:25, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > > Well, it sounds backwards to focus on the boot loader UI side of > > "recovery" so much if you don't even have any reasonably thing you > > could do in case of recovery better than a login prompt/shell... > > Well,

Re: [systemd-devel] Antw: [EXT] Re: Q: non-ASCII in syslog

On Do, 28.04.22 09:32, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > Actually I wasn't quite sure about the default config in SLES12. > It seems the flow is journald -> local rsyslogd -> remote syslogd > > > rsyslogd already knows if messages are UTF-8 because the system's $LANG > > (w

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

>>> Lennart Poettering schrieb am 27.04.2022 um 18:04 in Nachricht : > On Mi, 27.04.22 11:10, Neal Gompa (ngomp...@gmail.com) wrote: > >> > Rebooting from the DE has advantages: nice UI without much work, l10n, >> > accessibility, help, integration with normal auth mechanisms (e.g. polkit >> > au

Re: [systemd-devel] Antw: [EXT] Re: Q: non-ASCII in syslog

On Do, 28.04.22 09:37, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote: > > There's plenty software that doesn't support RFC 5425, and putting a > > BOM first is certainly not implemented in any of those. I think BOM is > > hideous and defaulting to UTF-8 generally safe. If we'd put BOM fir

[systemd-devel] multiple systemd-nspawn container name resolution

Hello, i have setup multiple systemd-nspawn container with virtualEthernet=yes. Inside the container systemd-networkd and systemd-resolved are enabled. So far so good. Is there a way to disable the 169.254... networking for systemd? The problem is as followed: ip r 169.254.0.0/16 dev ve-test

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

>>> Neal Gompa schrieb am 27.04.2022 um 17:26 in Nachricht : ... >> E.g. the biggest development in how the boot looks in recent years >> in Fedora has been hiding on the boot menus and boot messages by >> default. I.e. the _design_ is that you start with the logo of the >> manufacturer which is

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

On Mi, 27.04.22 18:57, Michael Biebl (mbi...@gmail.com) wrote: > >From https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996202#60 > > """ > we have recently discussed the matter of systemd-boot in > an upstream shim review gathering. Ominous. > We reject a signing of systemd-boot as > > * syste

Re: [systemd-devel] [EXT] Re: Q: non-ASCII in syslog

On Thu, Apr 28, 2022 at 10:32 AM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: > >>> Mantas Mikulenas schrieb am 27.04.2022 um 12:03 in > Nachricht > : > > On Wed, Apr 27, 2022 at 10:09 AM Ulrich Windl < > > ulrich.wi...@rz.uni-regensburg.de> wrote: > > > >> Hi! > >> > >> Having writte

[systemd-devel] Antw: [EXT] Re: Q: non-ASCII in syslog

>>> Lennart Poettering schrieb am 27.04.2022 um 13:10 in Nachricht : > On Mi, 27.04.22 09:09, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) > wrote: > >> Hi! >> >> Having written an RFC 3164 compatible syslog daemon, I noticed that systemd >> created syslog messages with non-ASCII characters.

[systemd-devel] Antw: [EXT] Re: Q: non-ASCII in syslog

>>> Mantas Mikulenas schrieb am 27.04.2022 um 12:03 in Nachricht : > On Wed, Apr 27, 2022 at 10:09 AM Ulrich Windl < > ulrich.wi...@rz.uni-regensburg.de> wrote: > >> Hi! >> >> Having written an RFC 3164 compatible syslog daemon, I noticed that systemd >> created syslog messages with non-ASCII cha