From owner-freebsd-questions  Mon Jul 21 01:15:10 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id BAA29563
          for questions-outgoing; Mon, 21 Jul 1997 01:15:10 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA29557
          for <freebsd-questions@freebsd.com>; Mon, 21 Jul 1997 01:15:08 -0700 (PDT)
Received: from tyree.iii.co.uk (tyree.iii.co.uk [193.117.77.66])
	by freefall.freebsd.org (8.8.6/8.8.5) with ESMTP id BAA13850
	for <freebsd-questions@freebsd.com>; Mon, 21 Jul 1997 01:13:27 -0700 (PDT)
Received: (from nik@localhost)
          by tyree.iii.co.uk (8.8.4/8.8.4)
	  id JAA11018; Mon, 21 Jul 1997 09:13:22 +0100 (BST)
Message-ID: <19970721091321.31479@iii.co.uk>
Date: Mon, 21 Jul 1997 09:13:21 +0100
From: Nik Clayton <nik@iii.co.uk>
To: Joshua Fielden <shag@concentric.net>
Cc: scott@statsci.com, Stan Brown <stanb@netcom.com>,
        Free BSD Questions list <freebsd-questions@freebsd.com>
Subject: Re: ppp loging with new user mode ppp
References: <199707190159.SAA18749@freefall.freebsd.org> <199707191621.JAA28191@knife.statsci.com> <33D1171E.46726BFC@concentric.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.76e
In-Reply-To: <33D1171E.46726BFC@concentric.net>; from Joshua Fielden on Sat, Jul 19, 1997 at 07:35:58PM +0000
Organization: interactive investor
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, Jul 19, 1997 at 07:35:58PM +0000, Joshua Fielden wrote:
> > Go look in your /var/log directory...when I did that I notice that I 
> > now have a ppp.tun0.log file in there...
> 
> I ended up doing an upgrade from 2.1.5 to 2.2.2 <06/18/97 release> and
> do not have a ppp.tun0.log, and my ppp.log is empty. When I do a fresh
> install of 2.2.2, I get the tun0 log, and it fills normally.

I'm guessing, but the log file will only be written to if it already exists.
If it doesn't, then nothing happens.

The fresh install of 2.2.2 probably created an empty log file, which then
filled up. Your upgrade didn't.

Of course, this doesn't solve the problem for anyone else, but it does
explain why it happened.

N
-- 
--+==[ Nik Clayton is Just Another Perl Hacker at Interactive Investor ]==+--
                               Pithy quotes suck.