Demonstrate the benefits of socket activation support

[zabbal]

The devices openwrt runs on are notorious for resource constraints. Hence would be nice to have patches for all the daemons like web interface or sshd to support socket activation: this way they will be started by systemd only when they are actually needed saving lots of cpu and memory otherwise.

[jdub]

I've done some work on socket activation support for Dropbear, but the version in OpenWrt doesn't have inetd support. In fact, someone actually went to the trouble of writing a patch to disable it. No idea why. So that experiment finished quickly. (I'll see if they accept changes.)

For now, this is a science experiment, so I'm going to muck around with packages that interest me, or that usefully demonstrate systemd features. I'm not ready to boil the combined OpenWrt technology and community oceans just yet. :-)

I'll leave this issue open as a reminder to have something that usefully demonstrates socket activation. Despite hurdles, I still reckon that's going to be Dropbear.

Thanks!