Well the article does suggest a mechanism to apply. As for the problem with SSH and login: You might well find that it is not the fork that is the problem. Yo

Well the article does suggest a mechanism to apply. As for the problem with SSH and login: You might well find that it is not the fork that is the problem. You might well be surprised at how much chaff is run by a login shell, or even by non-login shells. A case in point: I recently reduced the load on a server system that involved lots of SCP activity by noticing that, thanks to RedHat bug #810161, every SCP session even though it was a non-login non-interactive shell was first running a program to enumerate the PCI bus, to fix a problem with a Cirrus graphics adapter card that the machine did not have on a desktop environment that the machine did not have. This driven by /etc/bashrc sourcing /etc/profile.d/* . * https://github.com/FedoraKDE/kde-settings/blob/F-26/etc/profile.d/qt-graphicssystem.sh https://github.com/FedoraKDE/kde-settings/blob/F-26/etc/prof...