Systemd Development

• Thread Index

• 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]
  • From: Unknown
• 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]
  • From: Unknown
• 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: Unknown
• 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>
• Strange behavior of socket activation units
  • From: Tuukka Pasanen <pasanen.tuukka@xxxxxxxxx>
• Which distributions copy systemd-networkd 'link' files into the initramfs?
  • From: "Kevin P. Fleming" <kevin@xxxxxxx>
• Re: Udevd and dev file creation
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Nishant Nayan <nayan.nishant2000@xxxxxxxxx>
• Re: network interface scripting
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• network interface scripting
  • From: Kamil Jońca <kjonca@xxxxx>
• Re: OnCalendar weekday range syntax
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• OnCalendar weekday range syntax
  • From: Kenneth Porter <shiva@xxxxxxxxxxxxxxx>
• Failed to add PIDs to scope's control group: No such process
  • From: Gena Makhomed <gmm@xxxxxxxxx>
• Re: Configuring wakeup-online at runtime with networkctl
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Configuring wakeup-online at runtime with networkctl
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: network config breaks when starting a nspawn container
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: No space left errors on shutdown with systemd-homed /home dir
  • From: Neal Gompa <ngompa13@xxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Nishant Nayan <nayan.nishant2000@xxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Nishant Nayan <nayan.nishant2000@xxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Nishant Nayan <nayan.nishant2000@xxxxxxxxx>
• Passive vs Active targets
  • From: Thomas HUMMEL <thomas.hummel@xxxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [EXT] Re: systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: Launching script that needs network before suspend
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: Launching script that needs network before suspend
  • From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
• Re: Translating --machine parameter to a service file
  • From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
• Antw: [EXT] Udevd and dev file creation
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Antw: [EXT] Re: systemd killing processes on monitor wakeup?
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Antw: Re: [EXT] Re: Q: "systemd[1]: var-tmp-AP_0x6tWaHS.mount: Succeeded."
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Where to put unix sockets while SELinux enforces on init_t?
  • From: Daniel Farina <daniel@xxxxxx>
• Re: Udevd and dev file creation
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Nishant Nayan <nayan.nishant2000@xxxxxxxxx>
• Re: Where to put unix sockets while SELinux enforces on init_t?
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: Udevd and dev file creation
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Udevd and dev file creation
  • From: Nishant Nayan <nayan.nishant2000@xxxxxxxxx>
• Re: Where to put unix sockets while SELinux enforces on init_t?
  • From: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>
• Where to put unix sockets while SELinux enforces on init_t?
  • From: Daniel Farina <daniel@xxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: No space left errors on shutdown with systemd-homed /home dir
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: [EXT] Re: Q: "systemd[1]: var-tmp-AP_0x6tWaHS.mount: Succeeded."
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Antw: [EXT] Re: Q: "systemd[1]: var-tmp-AP_0x6tWaHS.mount: Succeeded."
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Q: "systemd[1]: var-tmp-AP_0x6tWaHS.mount: Succeeded."
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Q: "systemd[1]: var-tmp-AP_0x6tWaHS.mount: Succeeded."
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: No space left errors on shutdown with systemd-homed /home dir
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• network config breaks when starting a nspawn container
  • From: Francis Moreau <francis.moro@xxxxxxxxx>
• Re: systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: stacked extension not working
  • From: Umut Tezduyar Lindskog <Umut.Tezduyar@xxxxxxxx>
• Translating --machine parameter to a service file
  • From: Tomáš Hnyk <tomashnyk@xxxxxxxxx>
• Re: Launching script that needs network before suspend
  • From: Tomáš Hnyk <tomashnyk@xxxxxxxxx>
• Re: Rootless podman/buildah pull with systemd-homed fails -- important CAP dropped?
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: William Kennington <william@xxxxxxxxxxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>
• Re: Launching script that needs network before suspend
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Rootless podman/buildah pull with systemd-homed fails -- important CAP dropped?
  • From: Christian Brauner <brauner@xxxxxxxxxx>
• Re: Launching script that needs network before suspend
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Have I got circular dependencies?
  • From: "Kevin P. Fleming" <kevin@xxxxxxx>
• Re: Have I got circular dependencies?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Have I got circular dependencies?
  • From: "Kevin P. Fleming" <kevin@xxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: www <ouyangxuan10@xxxxxxx>
• Launching script that needs network before suspend
  • From: Tomáš Hnyk <tomashnyk@xxxxxxxxx>
• systemd killing processes on monitor wakeup?
  • From: Raman Gupta <rocketraman@xxxxxxxxx>
• Re: Have I got circular dependencies?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: Have I got circular dependencies?
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Have I got circular dependencies?
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: stacked extension not working
  • From: Luca Boccassi <bluca@xxxxxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: Dan Nicholson <dbn@xxxxxxxxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
• Re: sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: www <ouyangxuan10@xxxxxxx>
• sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: www <ouyangxuan10@xxxxxxx>
• sd_bus_process() + sd_bus_wait() is it not suitable for application?
  • From: www <ouyangxuan10@xxxxxxx>
• Rootless podman/buildah pull with systemd-homed fails -- important CAP dropped?
  • From: gmgod@xxxxx
• Google VRP - Payments Satisfaction Survey 2022
  • From: jakl@xxxxxxxxxx
• Re: homed: Issues with LUKS storage on btrfs
  • From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
• sd_bus_process() - ECONNRESET due to bus timeout?
  • From: Al Chu <chu11@xxxxxxxx>
• How to disable job cancelling feature
  • From: Prashantkumar dhotre <cdprashanth@xxxxxxxxx>
• Re: Antw: [EXT] [systemd‑devel] Why is using fstab the preferred approach according to systemd.mount man page?
  • From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
• Antw: [EXT] [systemd‑devel] Why is using fstab the preferred approach according to systemd.mount man page?
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Why is using fstab the preferred approach according to systemd.mount man page?
  • From: "Manuel Wagesreither" <ManWag@xxxxxxxxxxx>
• Re: Automatically moving forked processes in a different cgroup based on children's UID
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: How to check watchdog status?
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• How to check watchdog status?
  • From: Adam Nielsen <a.nielsen@xxxxxxxxxxx>
• Re: Automatically moving forked processes in a different cgroup based on children's UID
  • From: Michal Koutný <mkoutny@xxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: homed: Issues with LUKS storage on btrfs
  • From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Michael Biebl <mbiebl@xxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Michael Biebl <mbiebl@xxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• eth2: Failed to rename network interface 6 from 'eth2' to 'eno1': File exists
  • From: Harald Dunkel <harald.dunkel@xxxxxxxxxx>
• Re: Automatically moving forked processes in a different cgroup based on children's UID
  • From: Benjamin Berg <benjamin@xxxxxxxxxxxxxxxx>
• Re: Initial system date and time set by systemd
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Initial system date and time set by systemd
  • From: Sergei Poselenov <sposelenov@xxxxxxxxxxx>
• Automatically moving forked processes in a different cgroup based on children's UID
  • From: Wadih <wadih@xxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Context for "exitrd"
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Context for "exitrd"
  • From: Albert Brox <albert@xxxxxxxxxxx>
• EmitDNS and DNS attribute
  • From: yves baumes <ybaumes@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Antw: Re: Antw: [EXT] Re: the need for a discoverable sub-volumes specification
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Antw: [EXT] Re: the need for a discoverable sub-volumes specification
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Re: systemd v250 ignoring service.d overrides - service.d directories can no longer be a symlink?
  • From: Amish <anon.amish@xxxxxxxxx>
• Re: Antw: [EXT] Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: User authentication service isn't killed fully
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Re: User authentication service isn't killed fully
  • From: beroal <me@xxxxxxxxxxxx>
• Re: User authentication service isn't killed fully
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• systemd v250 ignoring service.d overrides - service.d directories can no longer be a symlink?
  • From: Amish <anon.amish@xxxxxxxxx>
• homed: Issues with LUKS storage on btrfs
  • From: Sebastian Wiesner <sebastian@xxxxxxxx>
• Re: Antw: Re: Antw: [EXT] Re: Q: journal logging and "{xyz}"
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Antw: Re: Antw: [EXT] Re: Q: journal logging and "{xyz}"
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Antw: [EXT] Re: Q: journal logging and "{xyz}"
  • From: Wols Lists <antlists@xxxxxxxxxxxxxxx>
• Antw: [EXT] Re: Q: journal filtering and unit failures
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Antw: [EXT] Re: Q: journal logging and "{xyz}"
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Antw: [EXT] Re: the need for a discoverable sub-volumes specification
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Antw: [EXT] Re: After= and Wants= doesn't seem to have an effect
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Antw: [EXT] Re: [systemd‑devel] Q: When will WorkingDirectory be checked?
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Q: journal filtering and unit failures
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Q: journal filtering and unit failures
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Q: journal logging and "{xyz}"
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Q: journal logging and "{xyz}"
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• User authentication service isn't killed fully
  • From: beroal <me@xxxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Steve Dodd <steved424@xxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Cristian Rodríguez <crrodriguez@xxxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Dave Howorth <systemd@xxxxxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Jonathan Kelly <jonkelly@xxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Scott Andrews <scott.andrews@xxxxxxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Mike Gilbert <floppym@xxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Jonathan Kelly <jonkelly@xxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Jonathan Kelly <jonkelly@xxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Andy Pieters <systemd@xxxxxxxxxxxxxxxxx>
• Re: After= and Wants= doesn't seem to have an effect
  • From: Christopher Wong <Christopher.Wong@xxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Jonathan Kelly <jonkelly@xxxxxxxxxxx>
• Re: asset failure that looks like it's coming from systemd/
  • From: Andy Pieters <systemd@xxxxxxxxxxxxxxxxx>
• asset failure that looks like it's coming from systemd/
  • From: Jonathan Kelly <jonkelly@xxxxxxxxxxx>
• systemd 250 released
  • From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
• Re: After= and Wants= doesn't seem to have an effect
  • From: Anita Zhang <the.anitazha@xxxxxxxxx>
• Managing systemd credentials
  • From: Joan Torres <joan.torres@xxxxxxxx>
• Re: After= and Wants= doesn't seem to have an effect
  • From: Christopher Wong <Christopher.Wong@xxxxxxxx>
• Re: throw routes are getting removed when networkd is restarted
  • From: Robert Dahlem <Robert.Dahlem@xxxxxxx>
• Re: systemd-timesyncd
  • From: Anita Zhang <the.anitazha@xxxxxxxxx>
• Re: throw routes are getting removed when networkd is restarted
  • From: Anita Zhang <the.anitazha@xxxxxxxxx>
• machined container console?
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>
• throw routes are getting removed when networkd is restarted
  • From: Robert Dahlem <Robert.Dahlem@xxxxxxx>
• Re: After= and Wants= doesn't seem to have an effect
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• systemd prerelease 250-rc3
  • From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
• Re: After= and Wants= doesn't seem to have an effect
  • From: Christopher Wong <Christopher.Wong@xxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: After= and Wants= doesn't seem to have an effect
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Q: When will WorkingDirectory be checked?
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• After= and Wants= doesn't seem to have an effect
  • From: Christopher Wong <Christopher.Wong@xxxxxxxx>
• Re: How to disable user@UID.service when starting gdm user
  • From: Adrian Vovk <adrianvovk@xxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Tim Safe <timsafeemail@xxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
• Q: When will WorkingDirectory be checked?
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• varlink external client
  • From: Vishwanath Chandapur <vishwavtu@xxxxxxxxx>
• How to disable user@UID.service when starting gdm user
  • From: "赵成义" <zhaochengyi@xxxxxxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Tim Safe <timsafeemail@xxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Tim Safe <timsafeemail@xxxxxxxxx>
• Re: Predictable Network Interface Name Bug?
  • From: Zbigniew Jędrzejewski-Szmek <zbyszek@xxxxxxxxx>
• Predictable Network Interface Name Bug?
  • From: Tim Safe <timsafeemail@xxxxxxxxx>
• Antw: Re: Antw: [EXT] Re: [systemd‑devel] the need for a discoverable sub‑volumes specification
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Antw: [EXT] Re: Additional Information for Ethernet
  • From: Spencer Ku (古世瑜) <Spencer.Ku@xxxxxxxxxxxx>
• Re: Additional Information for Ethernet
  • From: Spencer Ku (古世瑜) <Spencer.Ku@xxxxxxxxxxxx>
• Re: [systemd-networkd] Can use IPv6SendRA and IPv6AcceptRA in a same .network file
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• [systemd-networkd] Can use IPv6SendRA and IPv6AcceptRA in a same .network file
  • From: jackyzy823 <jackyzy823@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: Antw: [EXT] Re: [systemd‑devel] the need for a discoverable sub‑volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Antw: [EXT] Re: Additional Information for Ethernet
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• systemd prerelease 250-rc2
  • From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
• [RFC] Invitation from the OpenSSF's Great MFA Distribution project
  • From: "Robinson, Christopher" <christopher.robinson@xxxxxxxxx>
• Re: Additional Information for Ethernet
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• systemd prerelease 250-rc1
  • From: systemd tag bot <donotreply-systemd-tag@xxxxxxxxxx>
• [RFC] Invitation from the OpenSSF's Great MFA Distribution project
  • From: "Robinson, Christopher" <christopher.robinson@xxxxxxxxx>
• Additional Information for Ethernet
  • From: Spencer Ku (古世瑜) <Spencer.Ku@xxxxxxxxxxxx>
• Re: services stopping order during shutdown
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• services stopping order during shutdown
  • From: Prashantkumar dhotre <cdprashanth@xxxxxxxxx>
• systemd-resolved namespacing
  • From: Andrew Athan <aathan_systemd@xxxxxxxxxxxx>
• systemd-timesyncd
  • From: Scott Andrews <scott.andrews@xxxxxxxxxxxxxxx>
• Re: systemd-homed state dirty and not enough disk space
  • From: Lyubomir Parvanov <liubomirwm@xxxxxxxxx>
• Re: systemd-resolved namespacing
  • From: Petr Menšík <pemensik@xxxxxxxxxx>
• systemd-homed state dirty and not enough disk space
  • From: Lyubomir Parvanov <liubomirwm@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Wol <antlists@xxxxxxxxxxxxxxx>
• Re: How does udev determine onboard interface names
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Wol <antlists@xxxxxxxxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Adrian Vovk <adrianvovk@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Adrian Vovk <adrianvovk@xxxxxxxxx>
• How does udev determine onboard interface names
  • From: Ian Pilcher <arequipeno@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Wol <antlists@xxxxxxxxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: James Feeney <james@xxxxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Antw: [EXT] Re: [systemd‑devel] Run reboot as normal user
  • From: Mohamed Ali Fodha <fodha.mohamed.ali@xxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: James Feeney <james@xxxxxxxxxxx>
• Re: Antw: [EXT] Re: [systemd‑devel] Run reboot as normal user
  • From: Mohamed Ali Fodha <fodha.mohamed.ali@xxxxxxxxx>
• Re: Antw: [EXT] Re: [systemd‑devel] Run reboot as normal user
  • From: Mohamed Ali Fodha <fodha.mohamed.ali@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Adrian Vovk <adrianvovk@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Adrian Vovk <adrianvovk@xxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: James Feeney <james@xxxxxxxxxxx>
• Ordering services issue. Trying to start ptp4l in bonding setup fails as bonding appears to take a while.
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Antw: [EXT] Re: [systemd‑devel] Run reboot as normal user
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Antw: [EXT] Re: [systemd‑devel] Run reboot as normal user
  • From: Martin Wilck <mwilck@xxxxxxxx>
• systemd-resolved namespacing
  • From: Andrew Athan <aathan_systemd@xxxxxxxxxxxx>
• Antw: [EXT] Re: [systemd‑devel] Run reboot as normal user
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Run reboot as normal user
  • From: Martin Wilck <mwilck@xxxxxxxx>
• Antw: [EXT] Re: Authenticated Boot: dm-integrity modes
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Run reboot as normal user
  • From: Mohamed Ali Fodha <fodha.mohamed.ali@xxxxxxxxx>
• Re: Run reboot as normal user
  • From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
• Re: Run reboot as normal user
  • From: Mohamed Ali Fodha <fodha.mohamed.ali@xxxxxxxxx>
• Re: Run reboot as normal user
  • From: Colin Guthrie <gmane@xxxxxxxxxxxxxx>
• Re: Run reboot as normal user
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Run reboot as normal user
  • From: Mohamed Ali Fodha <fodha.mohamed.ali@xxxxxxxxx>
• Re: Authenticated Boot: dm-integrity modes
  • From: Wol <antlists@xxxxxxxxxxxxxxx>
• Authenticated Boot: dm-integrity modes
  • From: Adrian Vovk <adrianvovk@xxxxxxxxx>
• systemd boot timer problem
  • From: Wol <antlists@xxxxxxxxxxxxxxx>
• systemd boot timer problem
  • From: Wol <antlists@xxxxxxxxxxxxxxx>
• Re: [RFC] Switching to OpenSSL 3?
  • From: Dimitri John Ledkov <dimitri.ledkov@xxxxxxxxxxxxx>
• Re: [RFC] Switching to OpenSSL 3?
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: [RFC] Switching to OpenSSL 3?
  • From: Dimitri John Ledkov <dimitri.ledkov@xxxxxxxxxxxxx>
• Re: give unprivileged nspawn container write access to host wayland socket
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: give unprivileged nspawn container write access to host wayland socket
  • From: Nozz <nozz@xxxxxxxxxxxxxx>
• Re: give unprivileged nspawn container write access to host wayland socket
  • From: systemd-devel@xxxxxxxxxx
• give unprivileged nspawn container write access to host wayland socket
  • From: Nozz <nozz@xxxxxxxxxxxxxx>
• Antw: [EXT] Re: [systemd‑devel] the need for a discoverable sub‑volumes specification
  • From: "Ulrich Windl" <Ulrich.Windl@xxxxxxxxxxxxxxxxxxxx>
• Re: Networking in a systemd-nspawn container
  • From: Tobias Hunger <tobias.hunger@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Alvin Šipraga <ALSI@xxxxxxxxxxxxxxx>
• Re: Networking in a systemd-nspawn container
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: hardware conditional OS boot/load
  • From: Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Paul Menzel <pmenzel+systemd-devel@xxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: hardware conditional OS boot/load
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: How to get array[struct type] using sd_bus_message_* API's
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• How to get array[struct type] using sd_bus_message_* API's
  • From: Manojkiran Eda <manojkiran.eda@xxxxxxxxx>
• Re: Networking in a systemd-nspawn container
  • From: Jarosław Fedewicz <jaroslaw.fedewicz@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Alvin Šipraga <ALSI@xxxxxxxxxxxxxxx>
• Re: [RFC] Switching to OpenSSL 3?
  • From: Davide Cavalca <dcavalca@xxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Alvin Šipraga <ALSI@xxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
• hardware conditional OS boot/load
  • From: lejeczek <peljasz@xxxxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Andrei Borzenkov <arvidjaar@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: Systemd setup DSA interfaces in port mode and bond them together?
  • From: Mantas Mikulėnas <grawity@xxxxxxxxx>
• Systemd setup DSA interfaces in port mode and bond them together?
  • From: Brian Hutchinson <b.hutchman@xxxxxxxxx>
• Re: How to build a unified kernel for aarch64?
  • From: Zameer Manji <zmanji@xxxxxxxxx>
• Bug in older resolved breaks mDNS: help needed to identify commit that fixed it for backporting
  • From: Sergio Callegari <sergio.callegari@xxxxxxxxx>
• Re: How to build a unified kernel for aarch64?
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• How to build a unified kernel for aarch64?
  • From: Zameer Manji <zmanji@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Topi Miettinen <toiwoton@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <mzerqung@xxxxxxxxxxx>
• Re: [RFC] Switching to OpenSSL 3?
  • From: Michael Biebl <mbiebl@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Topi Miettinen <toiwoton@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Lennart Poettering <lennart@xxxxxxxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Topi Miettinen <toiwoton@xxxxxxxxx>
• Re: the need for a discoverable sub-volumes specification
  • From: Ludwig Nussel <ludwig.nussel@xxxxxxx>