From owner-freebsd-hackers Mon Jun 12 11:27:08 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA10251 for hackers-outgoing; Mon, 12 Jun 1995 11:27:08 -0700 Received: from mpp.com ([204.157.201.242]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA10244 for ; Mon, 12 Jun 1995 11:27:05 -0700 Received: (from mpp@localhost) by mpp.com (8.6.11/8.6.9) id NAA01263; Mon, 12 Jun 1995 13:26:03 -0500 From: Mike Pritchard Message-Id: <199506121826.NAA01263@mpp.com> Subject: Re: ntpdate To: fredriks@mcs.com (Lars Fredriksen) Date: Mon, 12 Jun 1995 13:26:02 -0500 (CDT) Cc: roberto@blaise.ibp.fr, hackers@freebsd.org In-Reply-To: from "Lars Fredriksen" at Jun 12, 95 12:36:03 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1046 Sender: hackers-owner@freebsd.org Precedence: bulk > Mike Pritchard writes: > [stuff deleted] > > I used to use ntpdate in my old SLIP scripts without any problems, > > but they only redirected stdin/out/err to /dev/null and ran > > in the background. Maybe some of the controlling tty stuff pppd is > > doing screws things up. > > I might be out of my leauge here, but I tend to agree that there is something > screwed up with the "Kerne" ppp line dicipline. You will notice that ping > in the background will do the same. I just saw an announcement in one of the Linux groups about a new version of pppd (2.1.2d), and one of the fixes was to reset all of the alarm masks back to default so that sendmail would work properly in the ip-up script. That sounded somewhat familar, so I applied the patch and sure enough, my ntpdate problem went away (ping started working in the ip-up script, too). So I guess after 2.0.5 gets out the door, we should upgrade pppd to the new version. -- Mike Pritchard mpp@legarto.minn.net "Go that way. Really fast. If something gets in your way, turn"