Re: [systemd-devel] L2TP NetDev not starting

On Wed, May 8, 2024 at 9:12 PM Tr4sK wrote: > > Hi, > I'm trying to get my head around to connect my debian box to a mikrotik > router. Mikrotik devices support Wireguard these days. It will outperform pretty much everything you want to use like 3x or something. Just probably don't want this at

Re: [systemd-devel] keeping a backup ESP partition in sync

On Fri, May 17, 2024, at 05:03, Alexander Gordeev wrote: > I think it is better to have them mounted as e.g. /boot/efi and > /boot/eficopy and make changes like this: > 1. update /boot/efi > 2. make sure the update is actually written to the device > 3. update /boot/eficopy > > Right now I do this

[systemd-devel] keeping a backup ESP partition in sync

Hi, I've tried systemd-boot recently, I like it a lot. Thanks! There is still one concern. I'd like to have a backup EFI partition because you know things can happen and my rootfs is on a mirror anyway. There is a popular approach with setting up a mdraid version 1.0 to sync the ESPs. I don't

[systemd-devel] systemd-run unset OnFailure property

I'm trying to add a global OnFailure= to all the services and excluding some non important services with /dev/null symlinks Now when using systemd-run in some cases I also don't want to run the OnFailure handler I tried (and multiple small variations) ``` systemd-run --unit=test

Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

Hi The modules need to be loaded using the services because there are several things that still do not autoload their modules. For instance, attempting an NFS mount over RDMA will fail unless the RDMA NFS module is pre-loaded. Thank you, Carolina Jubran From:

Re: [systemd-devel] Unexpected D-Bus timeout (https://github.com/systemd/systemd/issues/32381)

On Wed, May 15, 2024 at 4:38 PM Michal Sekletar wrote: > > On Wed, May 15, 2024 at 2:59 PM Michal Sekletar wrote: >> >> Hi everyone, >> >> I am currently struggling to understand why I am running into D-Bus related timeout on PID 1 API bus, which in turn causes systemd to transition the bus to

Re: [systemd-devel] Unexpected D-Bus timeout (https://github.com/systemd/systemd/issues/32381)

On Wed, May 15, 2024 at 2:59 PM Michal Sekletar wrote: > Hi everyone, > > I am currently struggling to understand why I am running into D-Bus > related timeout on PID 1 API bus, which in turn causes systemd to > transition the bus to BUS_CLOSING state and stop all Type=dbus services. > Here is a

Re: [systemd-devel] Unexpected D-Bus timeout (https://github.com/systemd/systemd/issues/32381)

On Wed, May 15, 2024 at 2:59 PM Michal Sekletar wrote: > Hi everyone, > > I am currently struggling to understand why I am running into D-Bus > related timeout on PID 1 API bus, which in turn causes systemd to > transition the bus to BUS_CLOSING state and stop all Type=dbus services. > Here is a

[systemd-devel] Unexpected D-Bus timeout (https://github.com/systemd/systemd/issues/32381)

Hi everyone, I am currently struggling to understand why I am running into D-Bus related timeout on PID 1 API bus, which in turn causes systemd to transition the bus to BUS_CLOSING state and stop all Type=dbus services. Here is a reproducer that was put together by Frantisek. #/bin/bash set -eux

[systemd-devel] systemd prerelease 256-rc2

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v256-rc2.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to

Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

Hi, may I ask why you need your own .service to load the module instead of using modules-load.d and modprobe.d? Just to understand your problem better. BR Silvio

Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

From: Andrei Borzenkov Sent: Sunday, May 12, 2024 6:44 PM To: Carolina Jubran ; systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate External email: Use caution opening links or

Re: [systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

On 12.05.2024 18:19, Carolina Jubran wrote: Hello! I need help with a systemd service that loads RDMA and InfiniBand drivers. The service unit specifies DefaultDependencies=no. However, when the service starts in initrd, it gets terminated when initrd-cleanup.service isolates for

[systemd-devel] Questions about initrd environment services and IgnoreOnIsolate

Hello! I need help with a systemd service that loads RDMA and InfiniBand drivers. The service unit specifies DefaultDependencies=no. However, when the service starts in initrd, it gets terminated when initrd-cleanup.service isolates for initrd-switch-root.target in the middle of the

[systemd-devel] Physical address of memory allocation in systemd-stub

Hi : Is there an already existing api that returns the underlying physical address of a chunk of memory allocated in systemd-stub? I am not sure of all the UEFI spec details and how memory allocation within the stub or PE executables are handled. thanks Ani

[systemd-devel] L2TP NetDev not starting

Hi, I'm trying to get my head around to connect my debian box to a mikrotik router. I tried to keep it simple and made it work with the ip l2tp commands. But, with the same parameter in a .netdev file it does not appear. To be clear, it's not a mikrotik issue. I gathered informations about

Re: [systemd-devel] soft-reboot and surviving it

Hi, attached is a better reproducer for the "broken pipe" problem, if applications write to stderr. This time without buffered glibc streams. If writing to stderr (fd 2) fails, the error get's logged via sd_journal_print(). Regards, Thorsten On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi

[systemd-devel] use a cache for resolving tags in libmount_parse() api

Hi Systemd-devel Team, I am trying to include a function mnt_new_cache() in systemd. I had changed the signature of a few existing function of systemd. I get the below compile error. kpit@L-16522:systemd$ ninja -C build ninja: Entering directory `build' [833/2203] Linking target systemd FAILED:

[systemd-devel] bootctl says ukify-generated efi file is not a UKI

Dear list, I'm generating UKIs with ukify via kernel-install (systemd version 255.4). These UKIs boot fine using systemd-boot. However, when using bootctl, I get unexpected output, the most important being that it says that the UKI efi files are not UKIs. Output of `bootctl list`: ```

Re: [systemd-devel] repart.d: Root partition not grown on Ubuntu 22.04 with *systemd* 249.11-0ubuntu3.12

Dear Nils, Thank you for the fast answer. Am 06.05.24 um 02:00 schrieb Nils Kattenbeck: This was not properly implemented until the current version: https://github.com/systemd/systemd/pull/30030 Indeed, it seems to work with Ubuntu 24.04 (noble numbat) with *systemd* 255.4-1ubuntu8. ```

Re: [systemd-devel] PropertiesChanged signal not sent unless Subscribe called

Hi, Carlos Garnacho: On Thu, Apr 11, 2024 at 11:45 PM segfault wrote: I noticed that some functionality of gnome-settings-daemon doesn't work as expected on some systems. I tracked that down to the fact that gnome-settings-daemon subscribes to the

Re: [systemd-devel] repart.d: Root partition not grown

This was not properly implemented until the current version: https://github.com/systemd/systemd/pull/30030 On Sun, May 5, 2024 at 10:15 PM Paul Menzel wrote: > > Dear systemd folks, > > > On Ubuntu 22.04 with *systemd-repart* 249.11-0ubuntu3.12, the root > partition in a qcow2 image, resized

[systemd-devel] repart.d: Root partition not grown

Dear systemd folks, On Ubuntu 22.04 with *systemd-repart* 249.11-0ubuntu3.12, the root partition in a qcow2 image, resized with qemu-img resize ubuntu-jammy.qcow2 +100G is not grown: $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sr0 11:01 1024M 0 rom

[systemd-devel] [User question] Unclear journal messages from systemd-resolved

Hi, I hope it’s OK to ask a question here (the About section said as much). I’m receiving messages in the journal that I have difficulty interpreting. It appears to repeatedly switch from TCP to UDP and back, claiming that both are a “degraded feature set”… Here is a sample journal output:

Re: [systemd-devel] MulticastDNS Responder Hostname in Early Boot

Yes, all of the command output was run within the initramfs, not the fully booted system. /etc/hostname exists in the initramfs. I ran a couple of tests using systemd.hostname as a kcmdline parameter: => cat /etc/hostname testvm => cat /proc/cmdline bgrt_disable systemd.hostname=testvm =>

Re: [systemd-devel] soft-reboot and surviving it

On Sat, Apr 20, 2024 at 8:21 PM Luca Boccassi wrote: > > On Sat, 20 Apr 2024 at 01:45, Cristian Rodríguez > wrote: > > > > On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > > > > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > > > wrote: > > > > > > > However, logging should work

Re: [systemd-devel] soft-reboot and surviving it

Sorry for the late response, we had a conference last week. On Sat, Apr 20, 2024 at 8:18 PM Luca Boccassi wrote: > Having no dependency on the rootfs is a core requirement that we > cannot change, the filesystem used is irrelevant. It's not going to > work, it will break immediately if you are

Re: [systemd-devel] MulticastDNS Responder Hostname in Early Boot

On Mon, Apr 29, 2024 at 9:16 AM Justin Brown wrote: > Hello, > > I'm having some trouble the resolved as a multicast DNS responder in early > boot. I'm trying to setup a headless system with full disk encryption, and > I need to connect remotely (currently using tinyssh) to unlock sysroot and >

[systemd-devel] MulticastDNS Responder Hostname in Early Boot

Hello, I'm having some trouble the resolved as a multicast DNS responder in early boot. I'm trying to setup a headless system with full disk encryption, and I need to connect remotely (currently using tinyssh) to unlock sysroot and other volumes before the boot continues. I use networkd to setup

[systemd-devel] question about systemd-tmpfiles-setup.service

Hi list, In some cases users may want to clean up the files under /tmp only during boot with the following configuration # cat /etc/tmpfiles.d/fs-tmp.conf #Type Path Mode User Group Age Argument d! /tmp 1777 root root 14d But according to the man page of tmpfiles.d ''' If the exclamation mark

[systemd-devel] Journal file disk usage on frequently rebooted systems ... again

I’m still slightly haunted by journal file disk space usage on a system with frequent reboots. Even after systemd issues #32248 and #32153, where I have assured @FabienRCT myself that journald does everything right. Here is a journal file that nicely shows my remaining doubts. User 2001 is used

Re: [systemd-devel] systemd prerelease 256-rc1

On Fr, 26.04.24 09:49, Neal Gompa (ngomp...@gmail.com) wrote: > > Well, people moved off split-usr quite successfully, which is a bigger > > feat than cleaning up the /boot/efi/ mess I'd say. > > > > Fedora is currently merging /usr/bin/ and /usr/sbin/, which I am pretty > > sure is a bigger

Re: [systemd-devel] systemd prerelease 256-rc1

On Fr, 26.04.24 09:47, Neal Gompa (ngomp...@gmail.com) wrote: > > > > * systemd-gpt-auto-generator will stop generating units for ESP > > > > or > > > > XBOOTLDR partitions if it finds mount entries for or below > > > > the /boot/ > > > > or /efi/ hierarchies in

Re: [systemd-devel] systemd prerelease 256-rc1

On Fri, Apr 26, 2024 at 9:46 AM Lennart Poettering wrote: > > On Fr, 26.04.24 10:39, Dan Nicholson (d...@endlessos.org) wrote: > > > On Fri, Apr 26, 2024 at 10:11 AM Adrian Vovk wrote: > > > > > > Perhaps Fedora can be adjusted to follow the BLS's recommended mount > > > points? > > > > The

Re: [systemd-devel] systemd prerelease 256-rc1

On Fri, Apr 26, 2024 at 9:41 AM Lennart Poettering wrote: > > On Do, 25.04.24 18:52, Neal Gompa (ngomp...@gmail.com) wrote: > > > > * systemd-gpt-auto-generator will stop generating units for ESP or > > > XBOOTLDR partitions if it finds mount entries for or below the > > >

Re: [systemd-devel] systemd prerelease 256-rc1

On Fr, 26.04.24 10:39, Dan Nicholson (d...@endlessos.org) wrote: > On Fri, Apr 26, 2024 at 10:11 AM Adrian Vovk wrote: > > > > Perhaps Fedora can be adjusted to follow the BLS's recommended mount points? > > The problem with all of these type of "we've realized a better way and > the old way is

Re: [systemd-devel] systemd prerelease 256-rc1

On Do, 25.04.24 18:52, Neal Gompa (ngomp...@gmail.com) wrote: > > * systemd-gpt-auto-generator will stop generating units for ESP or > > XBOOTLDR partitions if it finds mount entries for or below the > > /boot/ > > or /efi/ hierarchies in /etc/fstab. This is to

Re: [systemd-devel] systemd prerelease 256-rc1

On Fri, Apr 26, 2024 at 10:11 AM Adrian Vovk wrote: > > Perhaps Fedora can be adjusted to follow the BLS's recommended mount points? The problem with all of these type of "we've realized a better way and the old way is obsolete" is that it's left as someone else's issue to actually change

Re: [systemd-devel] systemd prerelease 256-rc1

systemd has been recommending against an arrangement like that for a long time now. These partitions are often fragile (read from bootloader code, or worse firmware! VFAT has no data integrity), and they really have no reason to be mounted unless they're about to be accessed. Stacking the mount

Re: [systemd-devel] systemd prerelease 256-rc1

On Thu, Apr 25, 2024 at 6:15 PM systemd tag bot wrote: > > A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the > tarball here: > > https://github.com/systemd/systemd/archive/v256-rc1.tar.gz > > NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production

[systemd-devel] systemd prerelease 256-rc1

A new systemd ☠️ pre-release ☠️ has just been tagged. Please download the tarball here: https://github.com/systemd/systemd/archive/v256-rc1.tar.gz NOTE: This is ☠️ pre-release ☠️ software. Do not run this on production systems, but please test this and report any issues you find to

Re: [systemd-devel] Fastest way to dump last X Mo of logs from the journal ?

Le jeu. 25 avr. 2024 à 08:38, Lennart Poettering a écrit : > > On Do, 25.04.24 12:49, Andy Pieters (syst...@andypieters.me.uk) wrote: > > > On Thu, 25 Apr 2024 at 12:48, Lennart Poettering > > wrote: > > > > > On Mi, 24.04.24 14:48, Etienne Champetier (champetier.etie...@gmail.com) > > > wrote:

Re: [systemd-devel] Prerequisites for systemd.volatile=yes

Hi All, Any inputs on this? -- Shedi On Mon, Apr 15, 2024 at 7:15 PM Shreenidhi Shedi < shreenidhi.sh...@broadcom.com> wrote: > Hi All, > > I'm trying to use volatile root feature for the first time. > > This is my /etc/fstab: > ``` > #system mnt-pt type options dump fsck >

Re: [systemd-devel] Fastest way to dump last X Mo of logs from the journal ?

On Do, 25.04.24 12:49, Andy Pieters (syst...@andypieters.me.uk) wrote: > On Thu, 25 Apr 2024 at 12:48, Lennart Poettering > wrote: > > > On Mi, 24.04.24 14:48, Etienne Champetier (champetier.etie...@gmail.com) > > wrote: > > > > > > what is "last X Mo" supposed to mean? is "mo" supposed to mean

Re: [systemd-devel] Fastest way to dump last X Mo of logs from the journal ?

On Thu, 25 Apr 2024 at 12:48, Lennart Poettering wrote: > On Mi, 24.04.24 14:48, Etienne Champetier (champetier.etie...@gmail.com) > wrote: > > > what is "last X Mo" supposed to mean? is "mo" supposed to mean months? > thus: show logs from a given number of most recent months? if so, just > use:

Re: [systemd-devel] Fastest way to dump last X Mo of logs from the journal ?

On Mi, 24.04.24 14:48, Etienne Champetier (champetier.etie...@gmail.com) wrote: > Hi all, > > sos report includes the last X Mo of logs, sometimes filtered, > sometimes not what is "last X Mo" supposed to mean? is "mo" supposed to mean months? thus: show logs from a given number of most recent

Re: [systemd-devel] Fastest way to dump last X Mo of logs from the journal ?

> On 24 Apr 2024, at 19:48, Etienne Champetier > wrote: > > Anyone have other ideas to do fast exports without having all logs in > memory or twice on disk ? Maybe base on time not size? Then you can use the --since option. Barry

[systemd-devel] Fastest way to dump last X Mo of logs from the journal ?

Hi all, sos report includes the last X Mo of logs, sometimes filtered, sometimes not right now it's doing the equivalent of "journalctl | tail -cXm", which reads / format all logs, which can be extremely slow The fastest way I found so far is: journalctl --reverse | head -c Xm | tac This still

Re: [systemd-devel] soft-reboot and surviving it

On Sat, 20 Apr 2024 at 01:45, Cristian Rodríguez wrote: > > On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > > wrote: > > > > > However, logging should work out of the box as long as the journal is > > > used, what problem are you

Re: [systemd-devel] soft-reboot and surviving it

On Fri, 19 Apr 2024 at 12:50, Thorsten Kukuk wrote: > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > wrote: > > On Fri, 19 Apr 2024 at 10:30, Thorsten Kukuk wrote: > > > > And now I started looking into how services can survive the > > > soft-reboot. I know the FOSDEM talk from Luca about

Re: [systemd-devel] soft-reboot and surviving it

On Fri, Apr 19, 2024 at 6:17 AM Thorsten Kukuk wrote: > > On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi > wrote: > > > However, logging should work out of the box as long as the journal is > > used, what problem are you seeing exactly? > > Starting around the shutdown and new start of

Re: [systemd-devel] Better systemd naming for Azure/MANA nic

+ systemd-devel@lists.freedesktop.org + dimitri.led...@surgut.co.uk From: Haiyang Zhang Sent: Tuesday, April 16, 2024 5:59 PM To: dimitri.led...@canonical.com Cc: Jack Aboutboul ; Sharath George John ; Luca Boccassi

Re: [systemd-devel] soft-reboot and surviving it

On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi wrote: > On Fri, 19 Apr 2024 at 10:30, Thorsten Kukuk wrote: > > And now I started looking into how services can survive the > > soft-reboot. I know the FOSDEM talk from Luca about this topic, but I > > don't like to move the application into

Re: [systemd-devel] soft-reboot and surviving it

On Fri, Apr 19, 2024 at 11:48 AM Luca Boccassi wrote: > However, logging should work out of the box as long as the journal is > used, what problem are you seeing exactly? Starting around the shutdown and new start of systemd-journald during soft-reboot, all writes to stderr will result in an

Re: [systemd-devel] soft-reboot and surviving it

On Fri, 19 Apr 2024 at 10:30, Thorsten Kukuk wrote: > > Hi, > > we finished the integration of soft-reboot into openSUSE Tumbleweed > and MicroOS (transactional-update), and the major problems except > firewalld+podman are solved. Now we only need to do all the "fine > tuning". > Is there

[systemd-devel] soft-reboot and surviving it

Hi, we finished the integration of soft-reboot into openSUSE Tumbleweed and MicroOS (transactional-update), and the major problems except firewalld+podman are solved. Now we only need to do all the "fine tuning". Is there meanwhile any reliable/official way to detect that this was a soft-reboot?

Re: [systemd-devel] (solved) Re: How to chain services driven by a timer?

On Thu, Apr 18, 2024 at 09:23:29AM -0600, Dan Nicholson wrote: > Since you likely don't have any units that depend on your service it > likely doesn't make a big difference. To demonstrate, here's a stupid > service I created: > > # cat /etc/systemd/system/foo.service > [Service] > Type=oneshot >

Re: [systemd-devel] (solved) Re: How to chain services driven by a timer?

On Thu, Apr 18, 2024 at 8:12 AM Brian Reichert wrote: > > On Wed, Apr 17, 2024 at 03:03:16PM -0600, Dan Nicholson wrote: > > I assume that this is just a script that does some post-processing on > > log files. In that case, I suggest that you use Type=oneshot with > > RemainAfterExit=no (the

Re: [systemd-devel] (solved) Re: How to chain services driven by a timer?

On Wed, Apr 17, 2024 at 03:03:16PM -0600, Dan Nicholson wrote: > I assume that this is just a script that does some post-processing on > log files. In that case, I suggest that you use Type=oneshot with > RemainAfterExit=no (the default). Then the service will actually wait > until your script

Re: [systemd-devel] Custom nobody user/group name not equivalent

On Wed, Apr 17, 2024 at 5:31 PM Lennart Poettering wrote: > This is a place where distros should not depart from each > other. Calling the user "nobody" and the group the same is simply the > least surprising thing: it's comonly understood that user's which have > their own matching groups should

Re: [systemd-devel] (solved) Re: How to chain services driven by a timer?

On Wed, Apr 17, 2024 at 2:49 PM Brian Reichert wrote: > > [Service] > Type=simple > > ExecStart=/usr/local/sbin/post-logrotate I assume that this is just a script that does some post-processing on log files. In that case, I suggest that you use Type=oneshot with RemainAfterExit=no (the

[systemd-devel] (solved) Re: How to chain services driven by a timer?

On Thu, Apr 11, 2024 at 11:14:20AM -0400, Brian Reichert wrote: > Let me wrap up some testing, and I'll report back if all is successful. I failed to report back; everything is working as I needed! I appreciate everyone's help here. For the record, my new service: 10-153-68-34:~ # cat

Re: [systemd-devel] Custom nobody user/group name not equivalent

On Mi, 17.04.24 17:17, Opty (opt...@gmail.com) wrote: > Hello, > > when using > > -8<- > -Dnobody-user=overflowuid \ > -Dnobody-group=overflowgid \ >

[systemd-devel] Custom nobody user/group name not equivalent

Hello, when using -8<- -Dnobody-user=overflowuid \ -Dnobody-group=overflowgid \ -8<- in Slackware I got

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

Hi, On Tue, Apr 16, 2024 at 04:03:25PM +0200, Lennart Poettering wrote: > On Di, 16.04.24 15:02, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > > > Hi, > > > > On Mon, Apr 15, 2024 at 05:41:00PM +0200, Lennart Poettering wrote: > > > Would be good to have that with systemd.log_target=debug, to

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

Hi, On Tue, Apr 16, 2024 at 04:03:25PM +0200, Lennart Poettering wrote: > On Di, 16.04.24 15:02, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > > > Hi, > > > > On Mon, Apr 15, 2024 at 05:41:00PM +0200, Lennart Poettering wrote: > > > Would be good to have that with systemd.log_target=debug, to

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

On Di, 16.04.24 15:02, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > Hi, > > On Mon, Apr 15, 2024 at 05:41:00PM +0200, Lennart Poettering wrote: > > Would be good to have that with systemd.log_target=debug, to see if > > tpm2.target even gets enqueued. > > Here is the verbose log: > >

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

Hi, On Mon, Apr 15, 2024 at 05:41:00PM +0200, Lennart Poettering wrote: > Would be good to have that with systemd.log_target=debug, to see if > tpm2.target even gets enqueued. Here is the verbose log:

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

On Mon, Apr 15, 2024 at 05:45:49PM +0200, Lennart Poettering wrote: > On Mo, 15.04.24 17:41, Lennart Poettering (lenn...@poettering.net) wrote: > > > > or the services needed for systemd-repart config with Encrypt=tpm2 > > > > Ah, repart is interesting. We are missing the tpm2.target dependency >

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

On Mo, 15.04.24 17:41, Lennart Poettering (lenn...@poettering.net) wrote: > > or the services needed for systemd-repart config with Encrypt=tpm2 > > Ah, repart is interesting. We are missing the tpm2.target dependency > there. That's a bug. Will fix. →

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

On Mo, 15.04.24 17:23, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > Hi, > > On Mon, Apr 15, 2024 at 04:02:46PM +0200, Lennart Poettering wrote: > > On Mo, 15.04.24 10:38, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > > > > > Hi, > > > > > > On Fri, Apr 12, 2024 at 05:03:18PM +0300,

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

Hi, On Mon, Apr 15, 2024 at 04:02:46PM +0200, Lennart Poettering wrote: > On Mo, 15.04.24 10:38, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > > > Hi, > > > > On Fri, Apr 12, 2024 at 05:03:18PM +0300, Aleksandar Kostadinov wrote: > > > Shouldn't the kernel automatically load the necessary

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

On Mo, 15.04.24 10:38, Mikko Rapeli (mikko.rap...@linaro.org) wrote: > Hi, > > On Fri, Apr 12, 2024 at 05:03:18PM +0300, Aleksandar Kostadinov wrote: > > Shouldn't the kernel automatically load the necessary modues when > > devices are detected... given proper udev rules and module > >

[systemd-devel] Prerequisites for systemd.volatile=yes

Hi All, I'm trying to use volatile root feature for the first time. This is my /etc/fstab: ``` #system mnt-pt type options dump fsck PARTUUID=ad7ab716-2c0a-4dbe-9a28-06dc8bd0383b / ext4 defaults,barrier,noatime,data=ordered 1 1 ``` And systemd grub configs are: systemd_cmdline=net.ifnames=0

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

Hi, On Fri, Apr 12, 2024 at 05:03:18PM +0300, Aleksandar Kostadinov wrote: > Shouldn't the kernel automatically load the necessary modues when > devices are detected... given proper udev rules and module > availability in the initrd filesystem? I guess it depends on how you > build your initrd

Re: [systemd-devel] Unclear as to why "exec" works but "oneshot" does not

On Sunday, 14 April 2024 at 15:21, Andrei Borzenkov wrote: > If whatever your script does involves (re-)starting of sshd service, you > have deadlock with "oneshot" - sshd service cannot proceed until your > service startup completes and your service apparently waits on something > that waits

Re: [systemd-devel] Unclear as to why "exec" works but "oneshot" does not

On 14.04.2024 16:48, Laura Smith wrote: I am running a simple service to tweak SSHD on first boot (the script is at the bottom of this mail). This is on Debian Bookworm incase it makes any difference. If I configure my service as: [Unit] Description=ITS Generate SSH Server Keys

[systemd-devel] Unclear as to why "exec" works but "oneshot" does not

I am running a simple service to tweak SSHD on first boot (the script is at the bottom of this mail). This is on Debian Bookworm incase it makes any difference. If I configure my service as: [Unit] Description=ITS Generate SSH Server Keys Wants=ssh.service Before=ssh.service [Service]

Re: [systemd-devel] Issues supporting systems with and without TPM and firmware TPM (was Re: Handle device node timeout?)

Shouldn't the kernel automatically load the necessary modues when devices are detected... given proper udev rules and module availability in the initrd filesystem? I guess it depends on how you build your initrd system for including them. On Wed, Apr 10, 2024 at 10:24 AM Mikko Rapeli wrote: > >

Re: [systemd-devel] PropertiesChanged signal not sent unless Subscribe called

Hi, On Thu, Apr 11, 2024 at 11:45 PM segfault wrote: > > Hi, > > I noticed that some functionality of gnome-settings-daemon doesn't work > as expected on some systems. I tracked that down to the fact that > gnome-settings-daemon subscribes to the >

Re: [systemd-devel] Serial console flow control will stuck systemd

On Fr, 12.04.24 09:33, 细石泉 (nicheln...@gmail.com) wrote: > systemd will write log to console directly when bootup. A unexpected serial > console flow control maybe block systemd at embedded systems. I guess > systemd doesn't do a good job of initializing the serial console. It doesn't do any job

[systemd-devel] Serial console flow control will stuck systemd

systemd will write log to console directly when bootup. A unexpected serial console flow control maybe block systemd at embedded systems. I guess systemd doesn't do a good job of initializing the serial console. If a noise XOFF(HEX13) generate when systemd bootup, systemd stucked. Should systemd

[systemd-devel] PropertiesChanged signal not sent unless Subscribe called

Hi, I noticed that some functionality of gnome-settings-daemon doesn't work as expected on some systems. I tracked that down to the fact that gnome-settings-daemon subscribes to the org.freedesktop.DBus.Properties.PropertiesChanged signal of org.freedesktop.systemd1 but doesn't call the

Re: [systemd-devel] How to chain services driven by a timer?

On Thu, Apr 11, 2024 at 04:58:05PM +0300, Andrei Borzenkov wrote: > There are no ordering dependencies between your services, so they are > started as soon as possible. if post-rotate.service must be started > after logrotate.service, it needs > > After=logrotate.service > > This is also needed

Re: [systemd-devel] How to chain services driven by a timer?

On Thu, Apr 11, 2024 at 4:17 PM Brian Reichert wrote: > > On Thu, Apr 11, 2024 at 11:16:36AM +0300, Andrei Borzenkov wrote: > > Show full unit definition for both logrotate.service and your service. > > Sure: > > 10-153-68-34:~ # cat /usr/lib/systemd/system/logrotate.service > [Unit] >

Re: [systemd-devel] How to chain services driven by a timer?

On Thu, Apr 11, 2024 at 11:16:36AM +0300, Andrei Borzenkov wrote: > Show full unit definition for both logrotate.service and your service. Sure: 10-153-68-34:~ # cat /usr/lib/systemd/system/logrotate.service [Unit] Description=Rotate log files Documentation=man:logrotate(8) man:logrotate.conf(5)

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, 10 Apr 2024 17:07:36 -0400 Brian Reichert wrote: > Hopefully someone here can assure me this is just due to an artifact > of bookkeeping. I'm specifically trying to avoid doing any work > while logrotate is running. I know it's a bodge, but put a short delay at the start of your

Re: [systemd-devel] How to chain services driven by a timer?

On Thu, Apr 11, 2024 at 12:07 AM Brian Reichert wrote: > > On Wed, Apr 10, 2024 at 01:47:47PM -0600, Dan Nicholson wrote: > > Restarting the timer doesn't make the service run immediately. Are you > > sure logrotate.service has run again since you made this change? Just > > simulate the timer and

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 01:47:47PM -0600, Dan Nicholson wrote: > Restarting the timer doesn't make the service run immediately. Are you > sure logrotate.service has run again since you made this change? Just > simulate the timer and start logrotate.service again. All the timer > does is activate

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 1:32 PM Brian Reichert wrote: > > On Wed, Apr 10, 2024 at 10:21:32PM +0300, Andrei Borzenkov wrote: > > On 10.04.2024 22:04, Brian Reichert wrote: > > > [Install] > > > WantedBy=logrotate.service > > > > > > > Links in [Install] section are created by "systemctl

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 01:29:10PM -0600, Dan Nicholson wrote: > On Wed, Apr 10, 2024 at 1:21???PM Andrei Borzenkov > wrote: > Just to be complete, your unit won't be triggered until you see it in > "systemctl show -p Wants logrotate.service". With > WantedBy=logrotate.service, you'll also find

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 10:21:32PM +0300, Andrei Borzenkov wrote: > On 10.04.2024 22:04, Brian Reichert wrote: > > [Install] > > WantedBy=logrotate.service > > > > Links in [Install] section are created by "systemctl enable". I could have sworn I did this, but did so (again) just to be sure:

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 1:21 PM Andrei Borzenkov wrote: > > On 10.04.2024 22:04, Brian Reichert wrote: > > On Wed, Apr 10, 2024 at 09:06:09AM -0600, Dan Nicholson wrote: > >> On Wed, Apr 10, 2024 at 8:50???AM Brian Reichert > >> wrote: > >>> > >>> My current service file: > >>> > >>>[Unit]

Re: [systemd-devel] How to chain services driven by a timer?

On 10.04.2024 22:04, Brian Reichert wrote: On Wed, Apr 10, 2024 at 09:06:09AM -0600, Dan Nicholson wrote: On Wed, Apr 10, 2024 at 8:50???AM Brian Reichert wrote: My current service file: [Unit] Description=Activities after logrotation Requires=logrotate.service

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 09:06:09AM -0600, Dan Nicholson wrote: > On Wed, Apr 10, 2024 at 8:50???AM Brian Reichert wrote: > > > > My current service file: > > > > [Unit] > > Description=Activities after logrotation > > > > Requires=logrotate.service > > Wants=logrotate.service > >

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 8:50 AM Brian Reichert wrote: > > My current service file: > > [Unit] > Description=Activities after logrotation > > Requires=logrotate.service > Wants=logrotate.service > After=logrotate.service > > [Service] > #Type=oneshot > Type=simple > >

Re: [systemd-devel] How to chain services driven by a timer?

On Wed, Apr 10, 2024 at 5:50 PM Brian Reichert wrote: > My goal is to implement a service that runs after logrotate.service > completes. > > logrotate.service is triggered by a timer logrotate.timer. > > I don't want to modify either of logrotate.service or logrotate.timer, > as they are

[systemd-devel] How to chain services driven by a timer?

My goal is to implement a service that runs after logrotate.service completes. logrotate.service is triggered by a timer logrotate.timer. I don't want to modify either of logrotate.service or logrotate.timer, as they are provided by the OS vendor (SLES 12 SP5, in my case.) I've tried to apply

Re: [systemd-devel] How to debug systemd services failing to start with 11/SEGV?

Hello Mantas, Am Wed, Apr 10, 2024 at 04:45:58PM +0300 schrieb Mantas Mikulėnas: > On Wed, Apr 10, 2024 at 4:08 PM Alexander Dahl wrote: > > > Note: platform here is 32 bit arm, namely v5te on Microchip SAM9X60 > > SoC. Kernel is 6.6, maybe I did not get the kernelconfig right and > > some

Re: [systemd-devel] How to debug systemd services failing to start with 11/SEGV?

On Wed, Apr 10, 2024 at 4:08 PM Alexander Dahl wrote: > Note: platform here is 32 bit arm, namely v5te on Microchip SAM9X60 > SoC. Kernel is 6.6, maybe I did not get the kernelconfig right and > some options are not set correctly? Or maybe those crashes are real? > Then I could need some help

  1   2   3   4   5   6   7   8   9   10   >