Racoon has a feautre when it's start an unprivileged process in a chroot directory. In this case the pid file created under the chroot dir, and the init script has a 'static' variable holding the pid file path. The worst is if I made a simlink for the pid file, the init script kills only the unprivileged process not the parent... So if you use the chroot + 'unprivileged user' feature, the only way to stop the racoon daemon is: `killall racoon`
Reopen with ebuild name and version... Not going to ponder which apps installs this.
Sorry about this... package: net-firewall/ipsec-tools-0.6.5 The init script: /etc/init.d/racoon And the relevant config section (from /etc/racoon/racoon.conf) privsep { user "racoon"; group "racoon"; chroot "/var/jail/racoon"; }
Created attachment 89295 [details, diff] racoon init script patch The simplest solution :)
Thanks.
For the record, I had this same problem with racoon running chrooted. Using the resolution in this bug and switching to "killall racoon" in the initscript resolved the problem for me. I propose that this change be put into portage, as I don't currently see it there.
better fix is hopefully in bug #151375