-
Notifications
You must be signed in to change notification settings - Fork 746
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
Support systemd socket activation for charon #2074
Comments
I remember in 2023 I still used systemctl start strongswan to start strongswan. Later, I didn't notice when it was started with the OS upgrade, and it became systemctl start strongswan-starter |
there's already systemd integration using charon-systemd. It doesn't use socket activation, but daemon status reporting. Isn't that enough? |
Thank you for your comment. Indeed I missed the Debian package charon-systemd, shipping:
In Debian that seems to be installed next to strongswan-starter, that cannot be purged without removing all the other strongSwan packages.
Both units have |
Using Debian sid/unstable with strongswan-starter 5.9.13-2, the package ships a systemd service unit:
It would be nice, if the daemon could be started via systemd socket activation.
PS: It looks like there was a discussion about this already ten years ago in the mailing list in the thread strongSwan, swanctl and systemd.
The text was updated successfully, but these errors were encountered: