id,summary,reporter,owner,description,type,status,priority,milestone,component,version,severity,resolution,keywords,cc 563,OpenVPN 2.3.7: using --management-hold causes PID file to not be written,kristov,Steffan Karger,"Since commit da9b292733e929a2900dc32d37f0424c3d588366 (f025de005d719201a69ad0313d545a1ddd244752 in release/2.3), if the OpenVPN daemon is startet with --management-hold, its PID file is not written. This is a regression to earlier versions which did write the PID file. I tested OpenVPN 2.3.7 (where the PID file is not written), and OpenVPN 2.3.6 as well as OpenVPN 2.3.7 with commit f025de005d719201a69ad0313d545a1ddd244752 being reverted, which both write the PID file. Looking at the changeset, it seems that the removal of calling do_init_first_time() (which creates the PID file) from within do_hold() leads to the erroneous behaviour. The PID file does get written as soon as the HOLD mode is left and the tunnel is started, but that's too late. The bug has been detected in the context of the fli4l router project (http://www.fli4l.de/en/), where OpenVPN is provided as the main tunnelling solution. The fli4l OpenVPN scripts use the PID file to determine whether the OpenVPN daemon is running before talking to it via the management port.",Bug / Defect,closed,minor,release 2.3.8,Generic / unclassified,OpenVPN 2.3.7 (Community Ed),"Not set (select this one, unless your'e a OpenVPN developer)",fixed,,