From owner-freebsd-questions Mon Sep 1 22:47:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA16646 for questions-outgoing; Mon, 1 Sep 1997 22:47:02 -0700 (PDT) Received: from gdi.uoregon.edu (cisco-ts15-line15.uoregon.edu [128.223.150.198]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA16640 for ; Mon, 1 Sep 1997 22:46:58 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id WAA03179; Mon, 1 Sep 1997 22:46:43 -0700 (PDT) Date: Mon, 1 Sep 1997 22:46:42 -0700 (PDT) From: Doug White X-Sender: dwhite@localhost Reply-To: Doug White To: andrew@ugh.net.au cc: questions@FreeBSD.ORG Subject: Re: EOF on /var/run/_secure from /etc/security In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 2 Sep 1997, Admin wrote: > I was wondering what would cause this (see below). I looked at > /etc/security and it appears that /var/run/_secure.15792 is created by > capturing the output of dmesg. Running dmesg off the command line works. > > Thanks, > > Andrew > > ---------- Forwarded message ---------- > > > > > > cmp: EOF on /var/run/_secure.15792 If this is the first time you've run /etc/security, it has to create yesterday's snapshot in /var/somethingorather :) and will EOF on that file. It should clear itself up; if not, you need to find the other file and make sure it isn't corrupted. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major Spam routed to /dev/null by Procmail | Death to Cyberpromo