[ntp:questions] Re: ntpd kills ppp/pppoe/DSL
mayer at gis.net
Thu Jun 16 17:46:29 UTC 2005
Take a look at https://ntp.isc.org/bugs/show_bug.cgi?id=413
which in turn references:
I suspect this is a similar problem with the newer Linux kernels.
----- Original Message Follows -----
> On Thu, 16 Jun 2005 07:36:17 +0100, David Woolley wrote:
> > In article <pan.2005.06.15.23.58.03.495303 at vakuum.de>,
> > "r.u" <ru at vakuum.de> wrote:
> >> router pppd: Terminating on signal 2.
> >> # ntpd -n -d -d -d -p /var/run/ntpd.pid
> >> addto_syslog: ntpd exiting on signal 2
> > Signal 2 is SIGINTR, i.e. a console interrupt (typically ^C or DEL).
> > It is not normally issued by ordinary programs, although it can be.
> > You have started ntpd in an attached mode. I don't know how you
> > have started pppd, or what shell you are using.
> > My guess is that you started pppd in a diagnostic mode, so that it
> > was still attached to the console, and simply backgrounded it with
> > &. You are probably using a non-job control shell, so ^C affects
> > background jobs (it is issued to a process group, when issued by
> > the terminal driver). You then interrupted your attached ntpd with
> > ^C causing collateral damage to the also attached pppd.
> > Your best way of running both diagnostically is to run them in
> > separate consoles. You can use nohup if it is supported by your
> Possibly I should have mentioned that I eventually terminated
> ntpd using ^C. Indeed, since I used the "-n" flag (don't fork),
> it was running in the foreground. In a different window I was
> monitoring the ppp connection, and when I saw that the ppp
> connection had died, there was no point in continuing to run
> ntpd, so I killed it. The point at which ntpd kills my ppp
> connection is somewhere much before the termination point.
> I included the diagnostic output of ntp because I thought it might
> shed some light on it's non-peaceful coexistence with ppp.
> questions mailing list
> questions at lists.ntp.isc.org
More information about the questions