Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.protocols.ppp > #44
| From | Avoid9Pdf@gmail.com |
|---|---|
| Newsgroups | comp.protocols.ppp, comp.os.linux.networking |
| Subject | Re: How2 kill pppd without pulling-plug? |
| Date | 2012-07-19 12:16 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <ju8tq6$9s6$1@dont-email.me> (permalink) |
| References | <ufcNr.4172$wD4.1838@newsfe19.iad> |
Cross-posted to 2 groups.
In article <ufcNr.4172$wD4.1838@newsfe19.iad>, James Carlson <carlsonj@workingcode.com> wrote:
> On 07/11/12 15:20, Avoid9Pdf@gmail.com wrote:
> > Here's `tail /var/log/messages` :-
> > Jul 11 19:08:50 localhost pppd[28712]: secondary DNS address 41.164.0.11 <-last good line
> > Jul 11 19:23:57 localhost kernel: usb.c: USB disconnect on device 00:0f.0-1 address 4
> > Jul 11 19:23:57 localhost kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000998
>
> The drivers clearly don't take kindly to having the hardware yanked
> away. If you have the source for the drivers and the time to
> investigate the problems they have, you might be able to repair them to
> your liking. Otherwise, don't do that.
>
I expect USB to be plug-and-play-able?
It was on my knl2.6* linux.
> > Also why can't I
> > `kill -9 <pppd-pid>` ?
>
> If a user thread (such as pppd) invokes a kernel interface that blocks,
> it can block in an uninterruptible manner. When that happens, you
> cannot kill the process because it can't be interrupted.
>
OK thanks, that's the deeper explanation that I wanted.
> In other words, it's due to the kernel bugs noted above that were
> triggered by the action of pulling out the USB cable on a live connection.
>
> > If I leave the USB-line connected it goes on-line by itself, every few minutes.
> > What the hell is that?!
>
> Dunno. Any chance you can post configuration information? By default,
> pppd doesn't do that, but there are options you can configure ("demand"
> and "persist" are the main ones) that will cause it to retry after a
> disconnect.
>
> Since it's not the default, it has to be somewhere in your pppd
> configuration files and/or command line options.
Adding `demand nopersist` to my 90s-old script, which I've
been using before I read your book at the Johannesburg
reference library [**], I'm now able to `killall pppd`.
And then I'm now able to pull-out the USB-line.
Which previously gave <kernel errors /problems> on this
knl 2.4*, since my knl 2.6* has crashed. Knl2.6* could handle it;
which is what also confused me.
I don't trust the system/s.
Going on line, is like a rocket-launch or a taxi-journey:
when it's finished, I must disconnect.
== Chris Glur.
[**] since the <revolutionary-natives-party> was handed
power, they've closed the previously brilliant ,30's built,
reference library, and I've heard that by mistake some
AA employee pulped many of the valuable books. A lot of the
new books are cartoon-based. Which perhaps makes sense
since the controlling-natives have never had a written language.
Today' BBC news was explaining how S. Italy's local government &
municipal authorities are similarly corrupt.
Be happy don't worry.
Back to comp.protocols.ppp | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How2 kill pppd without pulling-plug? Avoid9Pdf@gmail.com - 2012-07-11 19:20 +0000
Re: How2 kill pppd without pulling-plug? James Carlson <carlsonj@workingcode.com> - 2012-07-17 07:45 -0400
Re: How2 kill pppd without pulling-plug? Avoid9Pdf@gmail.com - 2012-07-19 12:16 +0000
Re: How2 kill pppd without pulling-plug? J G Miller <miller@yoyo.ORG> - 2012-07-19 12:27 +0000
csiph-web