SysVinit version 3.10 has successfully tackled the persistent bootlogd loop trouble. This update marks a significant development for SysVinit, the longstanding init system widely utilized in Unix-like operating environments.

Despite its enduring relevance, SysVinit has experienced a gradual decline in popularity due to the widespread adoption of systemd, a more contemporary init system offering enhanced features such as accelerated boot sequences, service management based on dependencies, process monitoring via control groups, and more.

The recent SysVinit 3.10 release introduces a pivotal bug fix, a new functionality, and documentation refinements, enhancing its overall usability.

Notably, the update incorporates support for the “machinectl stop” command. This command triggers a graceful shutdown (power-off) within a container by dispatching a SIGRTMIN+4 signal to PID 1 through systemd. SysVinit now recognizes this signal and responds by executing a shutdown command (shutdown -hP now), ensuring smoother shutdown operations for containers.

Furthermore, the latest version addresses a critical glitch concerning the bootlogd service, which previously encountered an infinite loop issue, leading to excessive CPU utilization.

The problem arose when bootlogd attempted to write to an opened device but was unsuccessful, causing it to repetitively open and close the device. The new resolution enables bootlogd to gracefully handle write failures, thereby averting the service from spiraling into an indefinite loop.

Additionally, SysVinit 3.10 incorporates enhancements to the shutdown.8 manual page, streamlining whitespace and special character usage. These adjustments enhance the clarity and user-friendliness of the documentation.

For detailed insights, consult the official changelog accompanying this latest SysVinit release.