Leasewatch uses wrong PID

GoogleCodeExporter commented 9 years ago

I use Tunnelblick version 3.0b22 on 10.6.1. When I start client.up.osx.sh
from my own up script, leasewatch uses the wrong PID (correct would be 3260
in this example):

Nov  4 10:54:38 user204 net.tunnelblick.openvpn.leasewatch[3427]:
/Applications/Tunnelblick.app/Contents/Resources/leasewatch: line 95: kill:
(3263) - No such process

This is probably due the fact that ${PPID} is the PID of my own up script.
Could you insert a new optional variable, so that I can append my ${PPID}
(from the openvpn process) to client.up.osx.sh. Thanks.

Original issue reported on code.google.com by dbert...@gmail.com on 4 Nov 2009 at 10:02

GoogleCodeExporter commented 9 years ago

I switched to use exec to solve this issue. So, you can close it unless you 
find an
easy way to get the right PID.

Original comment by dbert...@gmail.com on 19 Nov 2009 at 3:00

GoogleCodeExporter commented 9 years ago

Another way to do it would be to copy/paste the standard up/down scripts into 
your scripts at the point that you 
call them.

Original comment by jkbull...@gmail.com on 19 Nov 2009 at 3:06

Changed state: WontFix

GoogleCodeExporter commented 9 years ago

This is what I am currently doing. But I wait for the next release which uses my
deployed <config-name>.up.sh script automatically when activating "Set 
Nameserver".
Thanks anyway.

Original comment by dbert...@gmail.com on 19 Nov 2009 at 3:20

xingplus / tunnelblick

Leasewatch uses wrong PID #125