(jamesmui)
Date: Thursday, 16 January 2025 at 05:49
To: systemd-devel@lists.freedesktop.org
Subject: Re: [systemd-devel] systemd-bootchart, switch-root breakage
> Isn't systemd-bootchart, like, dead? Last release is nine years old or so.
The last release of systemd-bootchart, v235, was
> Isn't systemd-bootchart, like, dead? Last release is nine years old or so.
The last release of systemd-bootchart, v235, was done in November 2023:
https://github.com/systemd/systemd-bootchart/tags
There hasn’t been much activity lately, but I wouldn’t call it dead (there are
a few PRs open th
unsubscribe
On Thu, Jan 16, 2025 at 5:16 AM wrote:
> Isn't systemd-bootchart, like, dead? Last release is nine years old or so.
>
> Better use systemd-analyze instead.
>
> See
> https://wiki.archlinux.org/title/Improving_performance/Boot_process#Analyzing_the_boot_process
> for more information.
> I opened https://github.com/systemd/systemd-bootchart/issues/58 to track
> this.
Could someone explain why systemd-bootchart is being sent SIGHUP?
Changing systemd-bootchart to ignore that signal isn’t difficult, but I would
like to understand why PID 1 is sending it.
Note that systemd-boot
> **1. systemd-bootchart stops too early**
>
> According to "man systemd-bootchart", the recommended way to invoke bootchart
> is via a kernel parameter:
>
> init=/usr/lib/systemd/systemd-bootchart
>
> That parameter causes systemd-bootchart to be executed as the new init
> process when we swit
