Subject: Re: pppd & tail show PID after ppp-down
To: Gan Uesli Starling <oinkfreebiker@att.net>
From: Robert Elz <kre@munnari.OZ.AU>
List: netbsd-help
Date: 10/15/2001 18:59:07
    Date:        Mon, 15 Oct 2001 07:02:50 -0400
    From:        Gan Uesli Starling <oinkfreebiker@att.net>
    Message-ID:  <0110150702500B.00321@gus.starling.ws>

  | And I now have this script called out at the end of /etc/ppp/ppp-down for
  | the time being. But I'd like to get rid if it, if possible. Any ideas?

I'm only guessing as to what is happening here, but I assume that (almost)
the last thing that ppp-up does is run tail on some log file.   If so, nothing
is likely to make that go away other than explicitly killing it as you're
doing.   On the other hand, that might be not much more than a debug remnant
and perhaps just removing the tail from ppp-up will avoid the problems.

I'd also assume that just killing the tail would cause ppp-up to exit
as well, there's probably no need to kill it as well.

  | I am also a bit confused about when I do this on the laptop...
  | 
  | # dmesg | grep serial
  | com3 at pcmcia0 function 0 port 0x2e8-0x2ef: serial device
  | #
  | 
  | ...and something I read which said I need to translate from COM to TTY by
  | shifting toward zero so that,

That's when translating the wintrash COM names (where COM1 is first, etc).

Everywhere in NetBSD, including in the boot messages, you'll get 0 origin
numbering, so you're quite right the com3 there is the same as tty03.

  | Might there be a relationship to the above circumstance?

No, the processes hanging around is just the way (apparently) the ppp-up
script you're using is designed.

  | Or have I gone off-track, was that wrong what I read?

No, just a different context.

kre