From owner-freebsd-bugs  Wed Dec 23 01:12:00 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA17647
          for freebsd-bugs-outgoing; Wed, 23 Dec 1998 01:10:02 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA17589
          for <freebsd-bugs@FreeBSD.org>; Wed, 23 Dec 1998 01:09:59 -0800 (PST)
          (envelope-from gnats@FreeBSD.org)
Received: (from Unknown UID 563@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id BAA27316;
	Wed, 23 Dec 1998 01:10:01 -0800 (PST)
Date: Wed, 23 Dec 1998 01:10:01 -0800 (PST)
Message-Id: <199812230910.BAA27316@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Mike Holling <myke@ees.com>
Subject: Re:bin/8593:'uptime'behaviorvariesbyargzero
Reply-To: Mike Holling <myke@ees.com>
Sender: owner-freebsd-bugs@FreeBSD.org
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR bin/8593; it has been noted by GNATS.

From: Mike Holling <myke@ees.com>
To: freebsd-gnats-submit@freebsd.org, pauls@etext.org
Cc:  Subject: Re:bin/8593:'uptime'behaviorvariesbyargzero
Date: Wed, 23 Dec 1998 01:03:02 -0800 (PST)

 >   How-To-Repeat
 >          
 >$ uptime
 > 5:01PM  up 29 mins, 3 users, load averages: 0.00, 0.00, 0.00
 >$ /usr/bin/uptime
 > 5:01PM  up 29 mins, 3 users, load averages: 0.00, 0.00, 0.00
 >USER             TTY      FROM              LOGIN@  IDLE WHAT
 >pauls            p1       :0.0              4:33PM    36 -sh (csh)
 >pauls            p2       :0.0              4:33PM     - /usr/bin/uptime
 >pauls            p3       :0.0              4:33PM 2days -sh (csh)
 >$ ident /usr/bin/uptime
 >/usr/bin/uptime:
 >     $Id: fmt.c,v 1.12 1998/06/17 11:33:10 jkoshy Exp $
 >     $Id: pr_time.c,v 1.11 1997/12/28 17:50:10 alex Exp $
 >     $Id: w.c,v 1.28 1998/06/09 04:35:20 imp Exp $
 >
 >There is only one 'uptime' executable on the system, and 'uptime' is
 >'/usr/bin/uptime' in my $PATH.  System is 100% vanilla 3.0-RELEASE.
 >
 >   Audit-Trail
 >          
 >State-Changed-From-To: open-closed
 >State-Changed-By: steve
 >State-Changed-When: Sun Nov 8 17:19:32 PST 1998
 >State-Changed-Why:
 >Fixed in revision 1.29 of w.c.  Thanks!
 
 Unfortunately, the bug has resurfaced.  I cvsup'd shortly after
 midnight on 12/23/98, installed the new update, and get the same
 behavior (on an otherwise stock 3.0 system):
 
 {beach} /usr/bin# ident uptime
 uptime:
      $Id: pr_time.c,v 1.6.2.4 1998/03/08 14:31:51 jkh Exp $
      $Id: w.c,v 1.16.2.8 1998/12/14 06:04:44 dillon Exp $
 
 {beach} /usr/bin# uptime
  1:00AM  up 1 day, 12:23, 3 users, load averages: 0.04, 0.03, 0.04
 
 {beach} /usr/bin# /usr/bin/uptime
  1:00AM  up 1 day, 12:23, 3 users, load averages: 0.03, 0.03, 0.04
 USER             TTY      FROM              LOGIN@  IDLE WHAT
 root             p0       don.dw.lan       Mon01PM  2:30 -zsh (zsh)
 root             p1       net25-cust199.pd  8:09PM     - -zsh (zsh)
 root             p2       net25-cust199.pd 12:41AM     - /usr/bin/uptime
 
 {beach} /usr/bin# uname -a
 FreeBSD beach.dw.lan 3.0-RELEASE FreeBSD 3.0-RELEASE #1: Sun Dec 20
 00:01:10 PST 1998     don@beach.dw.lan:/usr/src/sys/compile/BEACH
 i386
 
 
 In particular, this mildly breaks one of the Big Brother scripts,
 which is how I stumbled across the bug...
 
 - Mike

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message