[MacPorts] #52525: openvpn2 startup script not working
MacPorts
noreply at macports.org
Thu Oct 6 19:31:12 CEST 2016
#52525: openvpn2 startup script not working
-------------------------------+--------------------------------
Reporter: thomas.hartwig@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.3.4
Resolution: | Keywords:
Port: openvpn2 |
-------------------------------+--------------------------------
Comment (by thomas.hartwig@…):
I have checked the plist file further and it turns out that you have to
specify the startup command in a single attribute. Further it looks like
all other parameters are not forwarded to the command itself. So I ended
up writing a wrapper script which contained all the parameters for
starting up openvpn correctly. So the final test script looks like below.
I created a openvpn2.sh which makes the call finally. I have also
activated some kind of debug to see what happens. However I do not know
how you usually realize startup things. IMHO there is a problem with
deamondo not forwarding the parameters correctly. But I am not an expert
in this.
{{{
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
"http://www.apple.com/DTDs/PropertyList-1.0.dtd" >
<plist version='1.0'>
<dict>
<key>Label</key><string>org.macports.openvpn2</string>
<key>ProgramArguments</key>
<array>
<string>/opt/local/bin/daemondo</string>
<string>--label=openvpn2</string>
<string>--start-cmd</string>
<string>/opt/local/sbin/openvpn2.sh</string>
<string>;</string>
<string>--pid=exec</string>
</array>
<key>Debug</key><false/>
<key>Disabled</key><false/>
<key>KeepAlive</key><true/>
<key>StandardOutPath</key>
<string>/tmp/logfile.log</string>
<key>StandardErrorPath</key>
<string>/tmp/error.log</string>
</dict>
</plist>
}}}
--
Ticket URL: <https://trac.macports.org/ticket/52525#comment:6>
MacPorts <https://www.macports.org/>
Ports system for the Mac operating system
More information about the macports-tickets
mailing list