I can reproduce this, and it seems obvious to me why this happens.
There doesn't appear to be any protection in place to prevent multiple instances of a given $NAME session from being spawned ... I just check the PID file /var/run/openvpn.$NAME.pid for existance. If it exists, fail to start, letting user know one is already started. Attached you'll find a patch file which can be applied to the openvpn-2.0.9-4 init script. -- Keith Kyzivat SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000
openvpn-init.patch
Description: Binary data
