Systemd Development
[Prev Page][Next Page]
- Re: Q: Start network in chroot?
- From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
- Wtrlt: Antw: [EXT] Re: Q: Start network in chroot?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Q: Start network in chroot?
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Q: Start network in chroot?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Unable to check 'effective' cgroup limits
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Unable to check 'effective' cgroup limits
- From: Lewis Gaul <lewis.gaul@xxxxxxxxx>
- resolve: mDNS test suite suggestions
- From: Vishal Chillara <chillara.vishal@xxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] cgroupsv2 and realtime processes
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: cgroupsv2 and realtime processes
- From: Michał Zegan <webczat@xxxxxxxxxxx>
- Re: cgroupsv2 and realtime processes
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: cgroupsv2 and realtime processes
- From: Michał Zegan <webczat@xxxxxxxxxxx>
- Re: cgroupsv2 and realtime processes
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: cgroupsv2 and realtime processes
- From: Michał Zegan <webczat@xxxxxxxxxxx>
- Re: cgroupsv2 and realtime processes
- From: Michal Koutný <mkoutny@xxxxxxxx>
- cgroupsv2 and realtime processes
- From: Michał Zegan <webczat@xxxxxxxxxxx>
- OnFailure units get triggered when service timesout on sigterm during restart of service
- From: Prashantkumar dhotre <cdprashanth@xxxxxxxxx>
- mkosi: Empty rpmdb after building older RPM distro on Fedora 36 host
- From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
- Re: No space left errors on shutdown with systemd-homed /home dir
- From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
- [libudev] is there a function to filter message from kernel with property and value
- From: "Wang, Yuan1" <yuan1.wang@xxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] MaxRetentionSec does not delete entries older than the specified time
- From: baba <for.ad@xxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] MaxRetentionSec does not delete entries older than the specified time
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- https://github.com/QubesOS/qubes-issues/issues/7335
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: MaxRetentionSec does not delete entries older than the specified time
- From: baba <for.ad@xxxxxxx>
- Re: MaxRetentionSec does not delete entries older than the specified time
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Re: MaxRetentionSec does not delete entries older than the specified time
- From: baba <for.ad@xxxxxxx>
- Re: MaxRetentionSec does not delete entries older than the specified time
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- MaxRetentionSec does not delete entries older than the specified time
- From: baba <for.ad@xxxxxxx>
- looping too fast
- From: lejeczek <peljasz@xxxxxxxxxxx>
- Re: Why are journal files stored in machine-specific directories?
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Why are journal files stored in machine-specific directories?
- From: Jakub Piecuch <j.piecuch96@xxxxxxxxx>
- v251 cryptsetup & FIDO2
- From: "Riccardo Paolo Bestetti" <pbl@xxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: Petr Menšík <pemensik@xxxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: Thomas Haller <thaller@xxxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: SCOTT FIELDS <Scott.Fields@xxxxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: SCOTT FIELDS <Scott.Fields@xxxxxxxxxxx>
- Re: certificate and trust store feature for systemd
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Looking for an example of using systemd-sysupdate with portable services
- From: "Xe Iaso" <me@christine.website>
- certificate and trust store feature for systemd
- From: SCOTT FIELDS <Scott.Fields@xxxxxxxxxxx>
- LLMNR priority over DNS
- From: Petr Menšík <pemensik@xxxxxxxxxx>
- Re: Questions around cgroups, systemd, containers
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: Configuring systemd to build systemd-tempfiles in Yocto
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: issues with systemd-cryptsetup@.service after in 251-rc3
- From: Dusty Mabe <dusty@xxxxxxxxxxxxx>
- "resolvectl -i INTERFACE query" fails if global DNS is used
- From: Wang Bing-hua <louiswpf@xxxxxxxxx>
- Configuring systemd to build systemd-tempfiles in Yocto
- From: Dave Glenton <Dave.Glenton@xxxxxxxxxxxxxxxx>
- Re: issues with systemd-cryptsetup@.service after in 251-rc3
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Questions around cgroups, systemd, containers
- From: Lewis Gaul <lewis.gaul@xxxxxxxxx>
- systemd 251 released
- From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
- Re: Questions around cgroups, systemd, containers
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: killmode
- From: Pascal <patatetom@xxxxxxxxx>
- Re: killmode
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: killmode
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: killmode
- From: Pascal <patatetom@xxxxxxxxx>
- Questions around cgroups, systemd, containers
- From: Lewis Gaul <lewis.gaul@xxxxxxxxx>
- Re: killmode
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: killmode
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- killmode
- From: Pascal <patatetom@xxxxxxxxx>
- Re: issues with systemd-cryptsetup@.service after in 251-rc3
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: issues with systemd-cryptsetup@.service after in 251-rc3
- From: Daan De Meyer <daan.j.demeyer@xxxxxxxxx>
- Re: issues with systemd-cryptsetup@.service after in 251-rc3
- From: Paul Menzel <pmenzel+systemd-devel@xxxxxxxxxxxxx>
- issues with systemd-cryptsetup@.service after in 251-rc3
- From: Dusty Mabe <dusty@xxxxxxxxxxxxx>
- Re: systemd-cryptsetup@.service crash during boot with fido2-device=auto
- From: Anton Hvornum <anton@xxxxxxxxxx>
- Re: systemd-cryptsetup@.service crash during boot with fido2-device=auto
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: systemd-cryptsetup@.service crash during boot with fido2-device=auto
- From: Anton Hvornum <anton@xxxxxxxxxx>
- systemd-cryptsetup@.service crash during boot with fido2-device=auto
- From: Anton Hvornum <anton@xxxxxxxxxx>
- Re: [RFC] Switching to OpenSSL 3?
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: [RFC] Switching to OpenSSL 3?
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: journalctl --vacuum-time does nothing
- From: baba <for.ad@xxxxxxx>
- Re: journalctl --vacuum-time does nothing
- From: František Šumšal <frantisek@xxxxxxxxx>
- journalctl --vacuum-time does nothing
- From: baba <for.ad@xxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Thomas Haller <thaller@xxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Dan Streetman <ddstreet@xxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Thomas Haller <thaller@xxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Dan Streetman <ddstreet@xxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Dusty Mabe <dusty@xxxxxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Dan Streetman <ddstreet@xxxxxxxx>
- Re: Execute a script/program at the start of a graphical session
- From: Dan Nicholson <dbn@xxxxxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Dusty Mabe <dusty@xxxxxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Thomas Haller <thaller@xxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Thomas Haller <thaller@xxxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: "Major Hayden" <major@xxxxxxxxxx>
- Re: Execute a script/program at the start of a graphical session
- From: Andrea Pappacoda <andrea@xxxxxxxxxxxx>
- Execute a script/program at the start of a graphical session
- From: Gerion Entrup <entrup@xxxxxxxxxxxxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Yeongjin Kwon <yeongjinkwon@xxxxxxxxx>
- [EFI-Stub][ARM64] Cannot load unified-kernel.efi using systemd EFI stub
- From: <Venkata.Pyla@xxxxxxxxxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Yuri Kanivetsky <yuri.kanivetsky@xxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Simon McVittie <smcv@xxxxxxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: Custom options and passing options via command line.
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Yuri Kanivetsky <yuri.kanivetsky@xxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Dusty Mabe <dusty@xxxxxxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Yuri Kanivetsky <yuri.kanivetsky@xxxxxxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: [SPAM] Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- Re: resolved vs. DNS servers listening on Linux dummy interfaces
- From: Peter Mattern <pmattern@xxxxxxxx>
- Re: Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Custom options and passing options via command line.
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: resolved vs. DNS servers listening on Linux dummy interfaces
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: resolved vs. DNS servers listening on Linux dummy interfaces
- From: Peter Mattern <pmattern@xxxxxxxx>
- Re: resolved vs. DNS servers listening on Linux dummy interfaces
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: resolved vs. DNS servers listening on Linux dummy interfaces
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: resolved vs. DNS servers listening on Linux dummy interfaces
- From: Petr Menšík <pemensik@xxxxxxxxxx>
- Should `MACAddressPolicy=persistent` for bridges/bonds/all-software-devices be reconsidered?
- From: Thomas Haller <thaller@xxxxxxxxxx>
- Re: [systemd] Behavior of "Requires" and "After" in service unit
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- [systemd] Behavior of "Requires" and "After" in service unit
- From: "Hamza, Muhammad" <Muhammad_Hamza@xxxxxxxxxx>
- Re: [systemd] Behavior of "Requires" and "After" in service unit
- From: "Hamza, Muhammad" <Muhammad_Hamza@xxxxxxxxxx>
- Custom options and passing options via command line.
- From: Kamil Jońca <kjonca@xxxxx>
- resolved vs. DNS servers listening on Linux dummy interfaces
- From: Peter Mattern <pmattern@xxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Yeongjin Kwon <yeongjinkwon@xxxxxxxxx>
- systemd prerelease 251-rc2
- From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Yeongjin Kwon <yeongjinkwon@xxxxxxxxx>
- Re: systemd tries to terminate a process that seems to have exited
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- systemd tries to terminate a process that seems to have exited
- From: Yuri Kanivetsky <yuri.kanivetsky@xxxxxxxxx>
- Re: Relationship between cgroup hierarchy and slice names
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Relationship between cgroup hierarchy and slice names
- From: Yeongjin Kwon <yeongjinkwon@xxxxxxxxx>
- Re: should random seeds go into /var/cache?
- From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: [EXT] Re: Q: logger: "invalid structured data parameter: 'fo\o="b\"a\"r"'"
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Antw: [EXT] Re: Q: logger: "invalid structured data parameter: 'fo\o="b\"a\"r"'"
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: should random seeds go into /var/cache?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Q: logger: "invalid structured data parameter: 'fo\o="b\"a\"r"'"
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Q: logger: "invalid structured data parameter: 'fo\o="b\"a\"r"'"
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- should random seeds go into /var/cache?
- From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
- Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Andrea Pappacoda <andrea@xxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Jóhann B. Guðmundsson <johannbg@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Jóhann B. Guðmundsson <johannbg@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: Antw: [EXT] [systemd‑devel] Query degraded state
- From: Barry <barry@xxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Starting transient services securely from other service without root
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] [systemd‑devel] Query degraded state
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: Re: Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Query degraded state
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Re: Starting transient services securely from other service without root
- From: Vašek Šraier <vaclav.sraier@xxxxxx>
- Re: Starting transient services securely from other service without root
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Starting transient services securely from other service without root
- From: Vašek Šraier <vaclav.sraier@xxxxxx>
- Re: Query degraded state
- From: Alvin Šipraga <ALSI@xxxxxxxxxxxxxxx>
- Query degraded state
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora
- From: Ian Pilcher <arequipeno@xxxxxxxxx>
- Re: [systemd‑devel] Antw: [EXT] Re: Q: non‑ASCII in syslog
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Waiting for all jobs to finish
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: Re: [systemd‑devel] Antw: [EXT] Re: Q: non‑ASCII in syslog
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Waiting for all jobs to finish
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Antw: Re: [EXT] Re: Q: non-ASCII in syslog
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Waiting for all jobs to finish
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: Q: non-ASCII in syslog
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Splitting sd‑boot from systemd/bootctl for enabling sd‑boot in Fedora
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: Q: non-ASCII in syslog
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- multiple systemd-nspawn container name resolution
- From: basti <mailinglist@xxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [EXT] Re: Q: non-ASCII in syslog
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Antw: [EXT] Re: Q: non-ASCII in syslog
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Q: non-ASCII in syslog
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Service Management and systemd Microconference @ Linux Plumbers
- From: Anita Zhang <the.anitazha@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Waiting for all jobs to finish
- From: Barry Scott <barry@xxxxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Starting transient services securely from other service without root
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Dan Nicholson <dbn@xxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Dan Nicholson <dbn@xxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Q: non-ASCII in syslog
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: Q: non-ASCII in syslog
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Q: non-ASCII in syslog
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Unit Names and Environment File Variable Names - Inconsistent Character Sets and Shortcomings with Unit Name Specifiers
- From: James Feeney <james@xxxxxxxxxxx>
- Splitting sd-boot from systemd/bootctl for enabling sd-boot in Fedora
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: juice <juice@xxxxxxxxxxx>
- Re: Antw: [EXT] Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: juice <juice@xxxxxxxxxxx>
- Antw: [systemd‑devel] Antw: [EXT] Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: juice <juice@xxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Re: rename a block device
- From: Pascal <patatetom@xxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: rename a block device
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- rename a block device
- From: Pascal <patatetom@xxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Re: Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Disallowing fingerprint authentication if pam_systemd_home.so needs a password
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Starting transient services securely from other service without root
- From: Vašek Šraier <vaclav.sraier@xxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Kenneth Porter <shiva@xxxxxxxxxxxxxxx>
- Re: LogsDirectory= permissions
- From: Andrea Pappacoda <andrea@xxxxxxxxxxxx>
- Re: LogsDirectory= permissions
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: Waiting for (transient) hostname configuration
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: LogsDirectory= permissions
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Dan Nicholson <dbn@xxxxxxxxxxxxx>
- Re: LogsDirectory= permissions
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- LogsDirectory= permissions
- From: Andrea Pappacoda <andrea@xxxxxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Alessio Igor Bogani <alessio.bogani@xxxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Sietse van Zanen <sietse@xxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Alessio Igor Bogani <alessio.bogani@xxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Waiting for (transient) hostname configuration
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Waiting for (transient) hostname configuration
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Waiting for (transient) hostname configuration
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Waiting for (transient) hostname configuration
- From: Alessio Igor Bogani <alessio.bogani@xxxxxxxxxx>
- Waiting for (transient) hostname configuration
- From: Alessio Igor Bogani <alessio.bogani@xxxxxxxxxx>
- Re: IPv6 RA/DHCPv6 support for nspawn?
- From: Nick Labich <nick@xxxxxxxxxx>
- IPv6 RA/DHCPv6 support for nspawn?
- From: ValdikSS <iam@xxxxxxxxxxxxxxx>
- Re: Apache APISIX on CentOS Linux release 7.9.2009 (Core)
- From: Tomasz Torcz <tomek@xxxxxxxxxxxxxx>
- Apache APISIX on CentOS Linux release 7.9.2009 (Core)
- From: Kaushal Shriyan <kaushalshriyan@xxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] device unit files
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] device unit files
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: device unit files
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: device unit files
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: device unit files
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Q: Forwarding journal to "remote" syslogd?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: device unit files
- From: Elbek Mamajonov <emm.boxinuse@xxxxxxxxx>
- Re: device unit files
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Linux Inlaws about systemd and init systems from 2th April 2022
- From: Luna Jernberg <droidbittin@xxxxxxxxx>
- Trying to Understand "journalctl --verify" and trigger some errors
- From: Yolo <yolo@xxxxxxxx>
- device unit files
- From: Elbek Mamajonov <emm.boxinuse@xxxxxxxxx>
- Re: trivial net connection logs - ?
- From: Ranbir Singh <japjitravel@xxxxxxxxx>
- Re: Starting one service when another one starts
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Starting one service when another one starts
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Starting one service when another one starts
- From: Nick Howitt <nick@xxxxxxxxxxxxx>
- Re: Samba Config Reload
- From: Simon McVittie <smcv@xxxxxxxxxxxxx>
- Re: Samba Config Reload
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: trivial net connection logs - ?
- From: Paul Menzel <pmenzel+systemd-devel@xxxxxxxxxxxxx>
- Re: trivial net connection logs - ?
- From: Tomasz Torcz <tomek@xxxxxxxxxxxxxx>
- Re: Samba Config Reload
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Intercepting/Delaying the boot process
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- trivial net connection logs - ?
- From: lejeczek <peljasz@xxxxxxxxxxx>
- Antw: [systemd‑devel] Antw: [EXT] Re: Samba Config Reload
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Samba Config Reload
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Intercepting/Delaying the boot process
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- systemd-resolved: Missing(?) DNS server info from systemd-networkd
- From: javud <javud@xxxxxxxxxxxx>
- Re: Samba Config Reload
- From: Leon Fauster <leonfauster@xxxxxxxxxxxxxx>
- Re: Samba Config Reload
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Starting one service when another one starts
- From: "Kevin P. Fleming" <kevin@xxxxxxx>
- Re: Samba Config Reload
- From: Yolo von BNANA <yolo@xxxxxxxx>
- Re: Starting one service when another one starts
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: Starting one service when another one starts
- From: Nick Howitt <nick@xxxxxxxxxxxxx>
- Re: Intercepting/Delaying the boot process
- From: Andreas Hartmann <hartan@xxxxx>
- Re: Starting one service when another one starts
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: Intercepting/Delaying the boot process
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Starting one service when another one starts
- From: Nick Howitt <nick@xxxxxxxxxxxxx>
- Re: Samba Config Reload
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Intercepting/Delaying the boot process
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Intercepting/Delaying the boot process
- From: Andreas Hartmann <hartan@xxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Luca Boccassi <luca.boccassi@xxxxxxxxx>
- Re: Intercepting/Delaying the boot process
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Antw: [EXT] Re: Dropping split-usr/unmerged-usr support
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Dropping split‑usr/unmerged‑usr support
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: Dropping split-usr/unmerged-usr support
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] all numeric usernames not allowed in systemd (version 245 onward)
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Dropping split‑usr/unmerged‑usr support
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: Re: Antw: Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Intercepting/Delaying the boot process
- From: Andreas Hartmann <hartan@xxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: "Jason A. Donenfeld" <Jason@xxxxxxxxx>
- Re: Samba Config Reload
- From: Kenneth Porter <shiva@xxxxxxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: all numeric usernames not allowed in systemd (version 245 onward)
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: all numeric usernames not allowed in systemd (version 245 onward)
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- all numeric usernames not allowed in systemd (version 245 onward)
- From: Nikhil Kshirsagar <nkshirsagar@xxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Luca Boccassi <luca.boccassi@xxxxxxxxx>
- Re: Samba Config Reload
- From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Luca Boccassi <luca.boccassi@xxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
- Re: Antw: Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Antw: Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Dropping split-usr/unmerged-usr support
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Mike Gilbert <floppym@xxxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Luca Boccassi <luca.boccassi@xxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: Luca Boccassi <luca.boccassi@xxxxxxxxx>
- Samba Config Reload
- From: Yolo von BNANA <yolo@xxxxxxxx>
- Antw: [EXT] Dropping split-usr/unmerged-usr support
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Kenneth Porter <shiva@xxxxxxxxxxxxxxx>
- Re: Dropping split-usr/unmerged-usr support
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Dropping split-usr/unmerged-usr support
- From: Luca Boccassi <luca.boccassi@xxxxxxxxx>
- Re: [EXT] Re: Q: journalctl -b -g logrotate
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Antw: [EXT] Re: Q: journalctl -b -g logrotate
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: nss-systemd
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: nss-systemd
- From: Gildas Bayard <gildas.bayard@xxxxxxxxxx>
- Re: nss-systemd
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Q: journalctl -b -g logrotate
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- nss-systemd
- From: Gildas Bayard <gildas.bayard@xxxxxxxxxx>
- Q: journalctl -b -g logrotate
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Systemd-bootchart doesn't generate CPU and Disk usage chart as in busybox bootchart
- From: "Karicheri, Murali" <Murali.Karicheri@xxxxxxxxx>
- [no subject]
- Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Q: Not "Reloading"?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Versioning generated files?
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: problem starting systemd in a container using parameters --default-standard-output=fd --default-standard-error=fd:stdout
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: udevadm: Failed to scan devices: Input/output error
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: udevadm: Failed to scan devices: Input/output error
- From: "Belal, Awais" <Awais_Belal@xxxxxxxxxx>
- Re: udevadm: Failed to scan devices: Input/output error
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: udevadm: Failed to scan devices: Input/output error
- From: "Belal, Awais" <Awais_Belal@xxxxxxxxxx>
- Re: udevadm: Failed to scan devices: Input/output error
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Outreachy contributor intro
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- udevadm: Failed to scan devices: Input/output error
- From: "Belal, Awais" <Awais_Belal@xxxxxxxxxx>
- problem starting systemd in a container using parameters --default-standard-output=fd --default-standard-error=fd:stdout
- From: masber masber <masber@xxxxxxxxxxx>
- systemd prerelease 251-rc1
- From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
- Re: Outreachy applicant
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Outreachy applicant
- From: Amarjargal Gundjalam <amarjargal16@xxxxxxxxx>
- Re: learning how to run systemd in a container, journal shows errors I would like to understand what they mean and why
- From: Daniel Walsh <dwalsh@xxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Outreachy Contributor Intro
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Outreachy Contributor Intro
- From: Rebecca Mckeever <rebecca.mckeever@xxxxxxxxxxxxxx>
- Re: #Outreachy contribution
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- #Outreachy contribution
- From: Formasit Fokunang <formasitf@xxxxxxxxx>
- Re: learning how to run systemd in a container, journal shows errors I would like to understand what they mean and why
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: learning how to run systemd in a container, journal shows errors I would like to understand what they mean and why
- From: masber masber <masber@xxxxxxxxxxx>
- learning how to run systemd in a container, journal shows errors I would like to understand what they mean and why
- From: masber masber <masber@xxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: /etc/os-release but for images
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: Marc Pervaz Boocha <mboocha@xxxxxxxxxxx>
- Re: Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: Neal Gompa <ngompa13@xxxxxxxxx>
- Re: Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] version bump of minimal kernel version supported by systemd?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: /etc/os-release but for images
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: version bump of minimal kernel version supported by systemd?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Dave Howorth <systemd@xxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: /etc/os-release but for images
- From: Davide Bettio <davide.bettio@xxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: /etc/os-release but for images
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: /etc/os-release but for images
- From: Davide Bettio <davide.bettio@xxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Luca Boccassi <bluca@xxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: /etc/os-release but for images
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: /etc/os-release but for images
- From: Davide Bettio <davide.bettio@xxxxxxxxxxxx>
- Q: Relying on exit code of journalctl -g ....
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: systemd move processes to user.slice cgroup after updating service configuration file
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: version bump of minimal kernel version supported by systemd?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- systemd move processes to user.slice cgroup after updating service configuration file
- From: "=?gb18030?b?zuHOqsTQ19M=?=" <csrenren@xxxxxx>
- Re: /etc/os-release but for images
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- version bump of minimal kernel version supported by systemd?
- From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
- Re: /etc/os-release but for images
- From: Christopher Obbard <chris.obbard@xxxxxxxxxxxxx>
- /etc/os-release but for images
- From: Davide Bettio <davide.bettio@xxxxxxxxxxxx>
- Re: find_device() and FOREACH_DEVICE_DEVLINK memory leaks on "systemd-249"
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: What is wrong with my .path setup?
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: What is wrong with my .path setup?
- From: John Ioannidis <systemd-devel@xxxxxxx>
- What is wrong with my .path setup?
- From: John Ioannidis <systemd-devel@xxxxxxx>
- networkd - how to set max WiFi transmit power level?
- From: Adam Nielsen <a.nielsen@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: Antw: [EXT] Re: Q: Difference between AssertPathExists and ConditionPathExists?
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Antw: [EXT] Re: Q: Difference between AssertPathExists and ConditionPathExists?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Q: Difference between AssertPathExists and ConditionPathExists?
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Q: Difference between AssertPathExists and ConditionPathExists?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- networkd: removing netdev files
- From: yves baumes <ybaumes@xxxxxxxxx>
- find_device() and FOREACH_DEVICE_DEVLINK memory leaks on "systemd-249"
- From: Tony Rodriguez <unixpro1970@xxxxxxxxx>
- Re: PrivateNetwork=yes is memory costly
- From: Christopher Wong <Christopher.Wong@xxxxxxxx>
- Re: How to grant systemd-nspawn access to USB device?
- From: Kevin P <petrilli.kevin@xxxxxxxxx>
- Re: How to grant systemd-nspawn access to USB device?
- From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
- Re: PrivateNetwork=yes is memory costly
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: PrivateNetwork=yes is memory costly
- From: Christopher Wong <Christopher.Wong@xxxxxxxx>
- Re: Antw: Re: [systemd‑devel] [EXT] Proposal to extend os‑release/machine‑info with field PREFER_HARDENED_CONFIG
- From: Stefan Schröder <stefan@xxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] PrivateNetwork=yes is memory costly
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: PrivateNetwork=yes is memory costly
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: How to grant systemd-nspawn access to USB device?
- From: Kevin P <petrilli.kevin@xxxxxxxxx>
- Re: How to grant systemd-nspawn access to USB device?
- From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
- networkd: changing priorities of default routing poilicy lists
- From: Marcel Menzel <mail@xxxxxx>
- How to grant systemd-nspawn access to USB device?
- From: Kevin P <petrilli.kevin@xxxxxxxxx>
- Re: making firewalld an early boot service
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: making firewalld an early boot service
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- EFI Boot default not honered
- From: Sietse van Zanen <sietse@xxxxxxxxx>
- Re: making firewalld an early boot service
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: making firewalld an early boot service
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: making firewalld an early boot service
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: making firewalld an early boot service
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- making firewalld an early boot service
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: "Manuel Wagesreither" <ManWag@xxxxxxxxxxx>
- PrivateNetwork=yes is memory costly
- From: Christopher Wong <Christopher.Wong@xxxxxxxx>
- Antw: Re: [systemd‑devel] Antw: [EXT] Re: timer "OnBootSec=15m" not triggering
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: timer "OnBootSec=15m" not triggering
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- How to verify that my ethernet interface is really reconfigured?
- From: "Jovic, Vladimir" <vladimir.jovic@xxxxxxx>
- Antw: [EXT] Re: timer "OnBootSec=15m" not triggering
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: timer "OnBootSec=15m" not triggering
- From: Peter Hoeg <peter@xxxxxxxx>
- Re: timer "OnBootSec=15m" not triggering
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- timer "OnBootSec=15m" not triggering
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Christopher Obbard <chris.obbard@xxxxxxxxxxxxx>
- Incomplete call stack logged by systemd-coredump
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Christopher Obbard <chris.obbard@xxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] How to find out the processes systemd‑shutdown is waiting for?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] [systemd‑devel] Q: journalctl ‑g
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] How to find out the processes systemd‑shutdown is waiting for?
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Q: journalctl -g
- From: Michael Chapman <mike@xxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] How to find out the processes systemd‑shutdown is waiting for?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Q: journalctl -g
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- [no subject]
- Re: systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- systemd failing to close unwanted file descriptors & FDS spawning and crashing
- From: Christopher Obbard <chris.obbard@xxxxxxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <felip@xxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: Daniel Walsh <dwalsh@xxxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: How to find out the processes systemd-shutdown is waiting for?
- From: Arian van Putten <arian.vanputten@xxxxxxxxx>
- Re: [EXT] [systemd‑devel] How to sychronize service START with STOP of mount units?
- From: "Manuel Wagesreither" <ManWag@xxxxxxxxxxx>
- How to find out the processes systemd-shutdown is waiting for?
- From: "Manuel Wagesreither" <ManWag@xxxxxxxxxxx>
- Antw: [EXT] Re: Journald: Re-use /var/log/journal hash entry after system upgrade
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: From dbus notification, how to know service entered failed state and will not start without admin action
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: Restarting "onshot" services
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Michal Koutný <mkoutny@xxxxxxxx>
- Re: Journald: Re-use /var/log/journal hash entry after system upgrade
- From: "Eric.Zaluzec@xxxxxxxxxx" <Eric.Zaluzec@xxxxxxxxxx>
- Re: Journald: Re-use /var/log/journal hash entry after system upgrade
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Syntax check for a new service?
- From: Tom Browder <tom.browder@xxxxxxxxx>
- Journald: Re-use /var/log/journal hash entry after system upgrade
- From: "Eric.Zaluzec@xxxxxxxxxx" <Eric.Zaluzec@xxxxxxxxxx>
- Re: Syntax check for a new service?
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Syntax check for a new service?
- From: Tom Browder <tom.browder@xxxxxxxxx>
- Re: Syntax check for a new service?
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Syntax check for a new service?
- From: Tom Browder <tom.browder@xxxxxxxxx>
- Re: Syntax check for a new service?
- From: Dave Howorth <systemd@xxxxxxxxxxxxxx>
- Syntax check for a new service?
- From: Tom Browder <tom.browder@xxxxxxxxx>
- Restarting "onshot" services
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Q: Wanting a target
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Q: Wanting a target
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Q: Perform action for reboots happen too frequently?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: Re: [systemd‑devel] [EXT] Proposal to extend os‑release/machine‑info with field PREFER_HARDENED_CONFIG
- From: Peter Hoeg <peter@xxxxxxxx>
- DeviceAllow=/dev/net/tun in systemd-nspawn@.service has no effect
- From: Gibeom Gwon <gb.gwon@xxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Silvio Knizek <killermoehre@xxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Barry <barry@xxxxxxxxxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <lipixx@xxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Silvio Knizek <killermoehre@xxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <lipixx@xxxxxxxxx>
- Re: unable to attach pid to service delegated directory in unified mode after restart
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- unable to attach pid to service delegated directory in unified mode after restart
- From: Felip Moll <lipixx@xxxxxxxxx>
- Re: From dbus notification, how to know service entered failed state and will not start without admin action
- From: Prashantkumar dhotre <cdprashanth@xxxxxxxxx>
- Re: [systemd‑devel] Q: Perform action for reboots happen too frequently?
- From: Silvio Knizek <killermoehre@xxxxxxx>
- [no subject]
- From dbus notification, how to know service entered failed state and will not start without admin action
- From: Prashantkumar dhotre <cdprashanth@xxxxxxxxx>
- Antw: Re: Antw: [EXT] Re: [systemd‑devel] Q: Perform action for reboots happen too frequently?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Re: [systemd‑devel] Q: Perform action for reboots happen too frequently?
- From: Silvio Knizek <killermoehre@xxxxxxx>
- Antw: Re: [systemd‑devel] [EXT] Proposal to extend os‑release/machine‑info with field PREFER_HARDENED_CONFIG
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] [RFC] systemd‑resolved: Send d‑bus signal after DNS resolution
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Q: Perform action for reboots happen too frequently?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Restart=on-failure and SuccessAction=reboot-force causing reboots on every exit of Main PID
- From: Michał Rudowicz <michal.rudowicz@xxxxxx>
- Antw: [EXT] Re: Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: [EXT] Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Peter Hoeg <peter@xxxxxxxx>
- Re: Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: [EXT] Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: [EXTERNAL] Re: [RFC] systemd-resolved: Send d-bus signal after DNS resolution
- From: Suraj Krishnan <surajkr@xxxxxxxxxxxxx>
- Re: [RFC] systemd-resolved: Send d-bus signal after DNS resolution
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Restart=on-failure and SuccessAction=reboot-force causing reboots on every exit of Main PID
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [RFC] systemd-resolved: Send d-bus signal after DNS resolution
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: [RFC] systemd-resolved: Send d-bus signal after DNS resolution
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Q: Perform action for reboots happen too frequently?
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Stefan Schröder <stefan@xxxxxxxxxxx>
- Q: Perform action for reboots happen too frequently?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] [systemd‑devel] How to sychronize service START with STOP of mount units?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- How to sychronize service START with STOP of mount units?
- From: "Manuel Wagesreither" <ManWag@xxxxxxxxxxx>
- Re: [RFC] systemd-resolved: Send d-bus signal after DNS resolution
- From: Dave Howorth <systemd@xxxxxxxxxxxxxx>
- Re: Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: [EXT] Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Stefan Schröder <stefan@xxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Restart=on-failure and SuccessAction=reboot-force causing reboots on every exit of Main PID
- From: Michał Rudowicz <michal.rudowicz@xxxxxx>
- Antw: [EXT] Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Re: Passive vs Active targets
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- [RFC] systemd-resolved: Send d-bus signal after DNS resolution
- From: Suraj Krishnan <surajkr@xxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Thomas HUMMEL <thomas.hummel@xxxxxxxxxx>
- Re: Passive vs Active targets
- From: Thomas HUMMEL <thomas.hummel@xxxxxxxxxx>
- Proposal to extend os-release/machine-info with field PREFER_HARDENED_CONFIG
- From: Stefan Schröder <stefan@xxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Kenneth Porter <shiva@xxxxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Kenneth Porter <shiva@xxxxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Thomas HUMMEL <thomas.hummel@xxxxxxxxxx>
- Re: Passive vs Active targets
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Passive vs Active targets
- From: Thomas HUMMEL <thomas.hummel@xxxxxxxxxx>
- Re: mdmon@md127 is stopped early
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: Re: Antw: [EXT] Service activation
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Service activation
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Antw: [EXT] Service activation
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: Antw: [EXT] Service activation
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Antw: [EXT] Service activation
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Service activation
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: Service activation
- From: Michael Biebl <mbiebl@xxxxxxxxx>
- Re: Service activation
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Service activation
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Service activation
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Service activation
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Service activation
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: systemd.sockets vs xinetd
- From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
- Re: [EXT] Re: [systemd‑devel] Run "ipmitool power cycle" after lib/systemd/system‑shutdown scripts
- From: Adam Nielsen <a.nielsen@xxxxxxxxxxx>
- Re: mdmon@md127 is stopped early
- From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxxxxxxxx>
- Antw: [EXT] Re: [systemd‑devel] Run "ipmitool power cycle" after lib/systemd/system‑shutdown scripts
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Adam Nielsen <a.nielsen@xxxxxxxxxxx>
- Antw: [EXT] Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Paul Menzel <pmenzel+systemd-devel@xxxxxxxxxxxxx>
- Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Adam Nielsen <a.nielsen@xxxxxxxxxxx>
- Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Paul Menzel <pmenzel+systemd-devel@xxxxxxxxxxxxx>
- Re: Converting xinetd files
- From: Paul Menzel <pmenzel+systemd-devel@xxxxxxxxxxxxx>
- Re: Converting xinetd files
- From: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>
- Re: Converting xinetd files
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Re: Converting xinetd files
- From: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>
- Converting xinetd files
- From: Wol <antlists@xxxxxxxxxxxxxxx>
- Antw: Re: Antw: Re: [EXT] Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: [EXT] Re: Help understanding "notify" (SLES15 SP3 restarting smartd)
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Antw: Re: [EXT] Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Antw: Re: [EXT] Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Failed to add PIDs to scope's control group: No such process
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Need a systemd unit example that checks /etc/fstab for modification and sends a text message
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Strange behavior of socket activation units
- From: Tuukka Pasanen <pasanen.tuukka@xxxxxxxxx>
- Re: [EXT] Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Etienne Champetier <champetier.etienne@xxxxxxxxx>
- Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Etienne Champetier <champetier.etienne@xxxxxxxxx>
- Re: [EXT] Re: Help understanding "notify" (SLES15 SP3 restarting smartd)
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: systemd-journald namespace persistence
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Strange behavior of socket activation units
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: mdmon@md127 is stopped early
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: Help understanding "notify" (SLES15 SP3 restarting smartd)
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Antw: [EXT] Re: Help understanding "notify" (SLES15 SP3 restarting smartd)
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: systemd.sockets vs xinetd
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
- Re: Help understanding "notify" (SLES15 SP3 restarting smartd)
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Help understanding "notify" (SLES15 SP3 restarting smartd)
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: systemd.sockets vs xinetd
- From: Michael Chapman <mike@xxxxxxxxxxxxxxxxx>
- systemd.sockets vs xinetd
- From: Yolo von BNANA <yolo@xxxxxxxx>
- Re: Strange behavior of socket activation units
- From: Tuukka Pasanen <pasanen.tuukka@xxxxxxxxx>
- Run "ipmitool power cycle" after lib/systemd/system-shutdown scripts
- From: Etienne Champetier <champetier.etienne@xxxxxxxxx>
- mdmon@md127 is stopped early
- From: Mariusz Tkaczyk <mariusz.tkaczyk@xxxxxxxxxxxxxxx>
- systemd-journald namespace persistence
- From: Roger James <roger@xxxxxxxxxxxxxxxxxxxxx>
- Antw: [EXT] Need a systemd unit example that checks /etc/fstab for modification and sends a text message
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Need a systemd unit example that checks /etc/fstab for modification and sends a text message
- From: Clinton Roy <clinton.roy@xxxxxxxxx>
- Need a systemd unit example that checks /etc/fstab for modification and sends a text message
- From: Tony Rodriguez <unixpro1970@xxxxxxxxx>
- Re: Odd behaviour on boot
- From: Tomasz Torcz <tomek@xxxxxxxxxxxxxx>
- Antw: Re: Antw: [EXT] [systemd‑devel] Why is using fstab the preferred approach according to systemd.mount man page?
- From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
- Re: Odd behaviour on boot
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Odd behaviour on boot
- From: Tomasz Torcz <tomek@xxxxxxxxxxxxxx>
- Re: Odd behaviour on boot
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Odd behaviour on boot
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Re: Odd behaviour on boot
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Antw: [EXT] [systemd‑devel] Why is using fstab the preferred approach according to systemd.mount man page?
- From: Thomas HUMMEL <thomas.hummel@xxxxxxxxxx>
- Re: Failed to add PIDs to scope's control group: No such process
- From: Gena Makhomed <gmm@xxxxxxxxx>
- Re: Odd behaviour on boot
- From: Mantas Mikulėnas <grawity@xxxxxxxxx>
- Odd behaviour on boot
- From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
- Re: Strange behavior of socket activation units
- From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
[Index of Archives]
[LARTC]
[Linux Security]
[Network Hardware]
[Bugtraq]
[Yosemite News]
[Samba]