Preston Smith wrote to Will Honea on 12-13-1999

PS> Hello Will!
PS> 
PS> Sunday December 12 1999 18:21, Will Honea wrote to Preston Smith:
PS> 
PS>  WH> I can't think of anything, Preston, unless it's a timing issue.  Try
a
PS>  WH> long pause between your end action and the pppkill call.  You might
PS>  WH> also learn something by removing the pppkill call from your script
then
PS>  WH> running it manually from a command line but it looks the same to me
as
PS>  WH> it's always been.
PS> 
PS> I called pppkill from an OS/2 box and it did not kill the session.
PS> 
PS> 
PS> I addewd this line to my script and remmed out the line that
PS> invioked pppkill 'start /fs /c /b go -ka ppp.exe'.  Bingo all went
PS> well - so  for some reason pppkill was not doing the job.
PS> 
PS> here i the data on the pppkill file on my system
PS> 
PS> 11-Dec-98 12:14     30690        49 pppkill.exe

Just tried this out and wouldn't you know it, pppkill does NOT see
ppp1 when InJoy has bound it.  Just for fun, try ifconfig ppp and
see what ppp interfaces are really open.  I do have a slightly
different pppkill.exe:

10-01-98  9:11a        48,719      0 a---  pppkill.exe

I am running TCP/IP 4.1 on this machine, so I doubt it will match
yours in detail.

Thinking back, I believe that it was determined at one time that
pppkill.exe would only kill sessions initiated by ppp.exe.  In fact,
writing this and thinking back I'm fairly certain that pppkill got the
pid to kill from a temp file written by ppp.exe which would make it's
usefullness a bit limited. Are you using DOIP to dial out (it uses
ppp.exe) or something else?  I use Injoy which does NOT use ppp.exe, so
that explains some of what I see here.
 
Will Honea 
--- Maximus/2 2.02