Re: [systemd-devel] Question: systemd-resolved.service delayed almost 90s start after systemd-sysctl.service

Hi, Paul more information for reference. Looking forward to your new reply.Thank you! 1.We changed the default startup Timeout to 60s in /etc/systemd/system.conf. DefaultTimeoutStartSec=60s more system.conf information for reference. [Manager] #LogLevel=info #LogTarget=journal-or-kmsg #LogColor

Re: [systemd-devel] Question: systemd-resolved.service delayed almost 90s start after systemd-sysctl.service

Hi, Paul Thank you for your reply. This is a low-probability, sporadic problem. Currently, there is no `journalctl -b` information with `debug` on the command line. The unit information of the two services is as follows: 1. systemctl cat systemd-resolved # /usr/lib/systemd/system/systemd-resolv

Re: [systemd-devel] Question: systemd-resolved.service delayed almost 90s start after systemd-sysctl.service

Dear Alien, Am 10.05.25 um 10:24 schrieb Alien Kong: I'm seeing an unexpected 90s delay between systemd-sysctl.service and systemd-resolved.service in our boot sequence (systemd 255.4-1ubuntu8.4, custom embedded board). systemd-analyze critical-chain shows: multi-user.target @1min 54.340s └─u

[systemd-devel] Question: systemd-resolved.service delayed almost 90s start after systemd-sysctl.service

Hello, I'm seeing an unexpected 90s delay between systemd-sysctl.service and systemd-resolved.service in our boot sequence (systemd 255.4-1ubuntu8.4, custom embedded board). systemd-analyze critical-chain shows: multi-user.target @1min 54.340s └─user_medium_priority.service @1min 32.653s +21.686s