3 ms·

systemd does this with socket-activated units.

• amelius 3y ago
  It doesn't work very well, though. Booting into a tty login prompt should be possible in well under 1 second. On a modern Linux system that uses systemd, however, it still takes on the order of a minute or more.
  • JdeBP 3y ago
    There's a lot of seemingly purely local infrastructure that nowadays depends from networking. login calls into a PAM module, which does database lookups, which goes through nsswitch and under the covers tries to consult nscd or systemd-resolved or some such, which either have network timeouts to tick down or aren't started until boot network interfaces are configured .... Mind you, there was the same issue with NIS.
    • amelius 3y ago
      Yes, I guess the problem is that laziness shouldn't stop at service boundaries.