| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007393 | Rocky-Linux-9 | systemd | public | 2024-07-11 18:54 | 2024-07-11 18:54 |
| Reporter | Julian Patocki | Assigned To | |||
| Priority | low | Severity | trivial | Reproducibility | always |
| Status | new | Resolution | open | ||
| Platform | x86_64 | OS | Rocky Linux | OS Version | 9.4 (Blue Onyx) |
| Summary | 0007393: Systemd displays 'no limit' instead of timeout in sec on reboot | ||||
| Description | Even though the 'DefaultTimeoutStopUSec' is set to 90 seconds, it is not being displayed in the message informing that the system waits for a system to stop: A stop job is running for Service ( 1s / no limit) It also does not change if TimoutStopSec is being configured within a unit itself. The timeout works correctly, only the message always displays 'no limit', instead of the acctual timeout value set. initially reported on the forum: by Sameer: https://forums.rockylinux.org/t/no-limit-on-systemd-stop-jobs/14983 | ||||
| Steps To Reproduce | To reproduce a small program in C that ignores signals can be compiled and than run as a systemd unit: #include <unistd.h> #include <signal.h> void ignore_signal(int sig) { } int main() { struct sigaction sa; memset(&sa, 0, sizeof(sa)); sa.sa_handler = SIG_IGN; sigaction(SIGINT, &sa, NULL); sigaction(SIGTERM, &sa, NULL); while (1) sleep(60); return 0; } /usr/lib/systemd/system/dummy.service [Unit] Description=Dummy Service that only waits for 60s After=default.target [Service] Type=simple ExecStart=/usr/local/bin/dummy Restart=on-failure RestartSec=5s [Install] WantedBy=multi-user.target The reboot needs to be initiated from the console. | ||||
| Tags | reboot, systemd, timeout | ||||
- Anonymous
