Can a more optimal method be found when rebooting or powering down to eliminate the long sleep pauses? When using other distros rebooting and powering down is fast. Very fast. I am well aware the other distros use systemd, but the pauses are annoying when compared to other distros.

Thanks.

1 members found this post helpful.

You can win at least 5 seconds giving the argument "fast" to halt or reboot. Beyond that, bear in mind that the script /etc/rc.d/rc.6 is written in such a way that it can handle a lot of use cases, and what is optimal for you may be not optimal for others. For this reason I suggest that instead of modifying it upstream for everyone you modify it locally.

Confirmed here. I think it's konsolepart since yakuake also shows these issues. Let's hope it's fixed in the next Release Service update or even sooner.

1 members found this post helpful.

I have modified the sleep commands for many years. The commands might have had merit with hardware from 25 years ago but are just annoying today.

You are sure?

Trust me as I speak from my own experience, that an Intel Atom driven mini-PC having the system in a SD card is not exactly a dragster...

And, wasn't already discussed in details that the systemd's boot/shutdown speed is irrelevant for Slackers? Let's keep our words.

Yes, any time the word systemd is mentioned some Slackers start frothing at the mouth. I don't care for systemd but even a blind hog occasionally finds the acorns. Nowhere did I hint or imply I wanted Slackware to move to systemd.

The comparison point was that anybody coming from a systemd distro will notice the significant pauses. The pauses are annoying. Yes, I remove the delays on my systems, but a global approach would be welcome. That is all my post was about. Hell.

Did you are sure that those pauses are irrelevant for a modern computer with 1GHz unicore processor and the system installed in a 5400 RPM hard drive, for example?

There are computers like this sold today, and slackware-current works on them.

I believe that Mr. Didier is right, and that those pauses may be irrelevant on your computers, but there's a guarantee that they are irrelevant for any computer able to run today the slackware-current? Probably not.

2 members found this post helpful.

The request is for a global solution. I don't know why systemd does not need these delays while Slackware does, but a configuration option in /etc/default that can be toggled would benefit everybody.

1 members found this post helpful.

https://kde.org/announcements/releas...2-apps-update/

Looks like this is needed:

https://github.com/ksnip/kImageAnnotator

Can it be considered for inclusion?

1 members found this post helpful.

The systemd does not need delays because it uses targets and parallel processing of the services. And service dependencies.

For example, it can simultaneous shutdown apache2, mysql, vsftpd services then it waits all of them to being down and pass to running another target.

Slackware have an old school linear startup/shutdown, where the services are started (or stopped) one after one. It is a total different thing. We should really compare them?

1 members found this post helpful.

I have a SlackBuild should you need one in the meantime.

I am not comparing the two approaches. I am only noting that anybody familiar with systemd will notice the delays. A global solution would be nice.

Yes, there is a good solution: an init system with parallel services handling and service dependencies resolution, like is OpenRC.

Feel free to ask our BDFL to switch Slackware to OpenRC.

1 members found this post helpful.

For most users, there's going to be a max of 10 seconds of "sleep" introduced in rc.6 (2 seconds for dhcpcd, 5 seconds between sending the SIGTERM and SIGKILL, and another 3 seconds to ensure harddrives have enough time to sync before powering off). Is that really that big of a deal? Those 10 seconds were introduced to prevent issues with the system or hard drives.

You say you aren't comparing systemd against Slackware but then state that "anyone familiar with systemd will notice the delays". That is a comparison. I don't care how fast or slow my system shuts down (within reason, no 5 minute shut downs or anything like that on a standard system), as long as it is shut down properly and all my data is preserved. Those 10 seconds that are introduced in rc.6 don't matter to me one bit.

2 members found this post helpful.

That would be nice. Is it published to SBo?

Anyway, I hope the third party could be included by Pat.

1 members found this post helpful.