Comment 7 for bug 271777
Revision history for this message
| Thierry Carrez (ttx) wrote Re: Exit status 127 when starting openvpn when its already started. | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hardy SRU Report
Bug impact: When openvpn is already started, trying to start it using the init script results in exit status 127. This can impact heartbeat deployments as mentionned in comment 5.
Versions affected: Hardy (openvpn initscript was rewritten in Intrepid)
Minimal patch: see comment 6 just above.
TEST CASE:
$ sudo apt-get install openvpn
Unpack the attached vpnconf.tar.gz into /etc/openvpn
$ sudo /etc/init.d/openvpn restart (should start the "server" VPN)
$ sudo /etc/init.d/openvpn start
Without the fix, fails with "/etc/init.
With the fix, warns with "server (FAILED - Already running (PID file exists).)" and exits with status 0
Regression potential:
Given the simplicity of the patch, regression potential is null. Nobody should have been relying on exit code 127 which was the result of a failed bash variable assignment.