Re: [systemd-devel] fstab generator/capture.mount randomly fails which depend of cryptsetup.target

On Do, 16.01.25 22:06, Sumit Kumar (sumit.kum...@trellix.com) wrote: > Hi Lennart, > Thanks for the reply. > > System is not always going in emergency mode, sometimes it boots > successfully. > But when the system goes in emergency mode we can see this unit is masked. > We are not masking the cryp

Re: [systemd-devel] Template unit : specifier validity

On 1/16/25 4:29 PM, Lennart Poettering wrote: On Do, 16.01.25 11:31, Thomas HUMMEL (thomas.hum...@pasteur.fr) wrote: Hello, Is the %i (or %I) specifier supposed to be valid for a template service unit for the Require= and After= directives ? It does not seem so in my tests Documentation state

Re: [systemd-devel] fstab generator/capture.mount randomly fails which depend of cryptsetup.target

Hi Lennart, Thanks for the reply. System is not always going in emergency mode, sometimes it boots successfully. But when the system goes in emergency mode we can see this unit is masked. We are not masking the cryptsetup.target file. Regards, Sumit Kumar On Thu, Jan 16, 2025 at 9:08 PM Lennart

Re: [systemd-devel] fstab generator/capture.mount randomly fails which depend of cryptsetup.target

On Do, 16.01.25 14:18, Sumit Kumar (sumit.kum...@trellix.com) wrote: > Hi , > > Our Linux based system uses an external storage disk called capture. > The capture disk is encrypted with LUKS to protect stored data. During > system boot, system uses the LUKS utilities to decrypt the disk before > m

Re: [systemd-devel] Template unit : specifier validity

On Do, 16.01.25 11:31, Thomas HUMMEL (thomas.hum...@pasteur.fr) wrote: > Hello, > > Is the %i (or %I) specifier supposed to be valid for a template service unit > for the Require= and After= directives ? > It does not seem so in my tests > > Documentation states: > "you may use the special "%i" sp

Re: [systemd-devel] Template unit : specifier validity

Hi, systemd itself already uses them in those sections without problems so they should definitely work: systemd-zram-setup@.service:After=dev-%i.device systemd-journald@.service:Requires=systemd-journald@%i.socket systemd-journald-varlink@%i.socket systemd-journald@.service:After=systemd-journald@

[systemd-devel] error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1

Hi, I get this error on an Ubuntu 22.04.5 when I try to connect via X2go from a Windows Box. The error message appears in the file .xsession-x2go-bioinformatics-mcd-01-errors in my home directory. When I connect, a X2go window appears but is closed some seconds later. In other cases, the window

[systemd-devel] Template unit : specifier validity

Hello, Is the %i (or %I) specifier supposed to be valid for a template service unit for the Require= and After= directives ? It does not seem so in my tests Documentation states: "you may use the special "%i" specifier in many of the configuration options" but don't seem to detail which one e

Re: [systemd-devel] fstab generator/capture.mount randomly fails which depend of cryptsetup.target

On Thu, Jan 16, 2025 at 03:00:23PM +0600, Chowdhury Tafsir Ahmed Siddiki wrote: > How to unsubscribe from here? The information is in headers: List-Unsubscribe: ,

Re: [systemd-devel] fstab generator/capture.mount randomly fails which depend of cryptsetup.target

How to unsubscribe from here? On Thu, Jan 16, 2025, 2:56 PM Sumit Kumar wrote: > Hi , > > Our Linux based system uses an external storage disk called capture. > The capture disk is encrypted with LUKS to protect stored data. During > system boot, system uses the LUKS utilities to decrypt the dis

[systemd-devel] fstab generator/capture.mount randomly fails which depend of cryptsetup.target

Hi , Our Linux based system uses an external storage disk called capture. The capture disk is encrypted with LUKS to protect stored data. During system boot, system uses the LUKS utilities to decrypt the disk before mounting the file systems containing the stored data. Due to an issue with inconsi

Re: [systemd-devel] systemd-bootchart, switch-root breakage

systemd-analayze plot can be misleading if you are trying to optimize the start up times. It is great for startup sequence dependencies and wall clock, but the times shown there are not reflecting the CPU utilization (AFAIK). I wasn’t aware of systemd-bootchart program (Thanks James). Couple of