Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Demonstrate the benefits of socket activation support #2

Open
zabbal opened this issue Feb 17, 2015 · 1 comment
Open

Demonstrate the benefits of socket activation support #2

zabbal opened this issue Feb 17, 2015 · 1 comment

Comments

@zabbal
Copy link

zabbal commented Feb 17, 2015

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
Copy link
Owner

jdub commented Feb 19, 2015

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!

@jdub jdub changed the title socket activation support Demonstrate the benefits of socket activation support Feb 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants