From owner-freebsd-questions Tue Apr 9 13:24: 0 2002 Delivered-To: freebsd-questions@freebsd.org Received: from cheetah.shortcircut.org (244-87-189-66.wo.cpe.charter-ne.com [66.189.87.244]) by hub.freebsd.org (Postfix) with ESMTP id 623F737B404 for ; Tue, 9 Apr 2002 13:23:55 -0700 (PDT) Received: from there (bogin@h00104b63ea48.ne.client2.attbi.com [24.147.249.96]) by cheetah.shortcircut.org (8.12.2/8.11.6) with SMTP id g39KpPMH091172 for ; Tue, 9 Apr 2002 16:51:27 -0400 (EDT) (envelope-from bogin@shortcircut.org) Message-Id: <200204092051.g39KpPMH091172@cheetah.shortcircut.org> Content-Type: text/plain; charset="iso-8859-1" From: Mike Bohan Reply-To: bogin@shortcircut.org To: freebsd-questions@freebsd.org Subject: question on problem with w/uptime. Date: Tue, 9 Apr 2002 16:24:08 -0400 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello there, Recently I've run into a little problem with w/uptime, which of course are equivalent programs other than their arguements. Since a picture tells many words, here's an output of the problem to illustrate it. $ w w: /dev/:0: No such file or directory 4:12PM up 19:57, 4 users, load averages: 0.01, 0.03, 0.00 USER TTY FROM LOGIN@ IDLE WHAT bogin p1 :0.0 11:34AM 13 ssh As you can see, the w program performs all the operations it should, but leaves that curious error message. I first noticed the problem after cvsuping and building world a few days ago. Thinking that perhaps there was a bug in a recent date of -stable, I recompiled with older code. This did not solve the problem however, so I can only conclude that it must have been something that I broke. I breifly looked at the w/uptime source code to see if there was anything obvious, but that didn't lead me anywhere. Does anyone have any idea why it would be trying to open /dev/:0:? That of course is not a valid device, so I'm guessing the wrong parameters are being fed into the program. If anyone has any ideas of something that could cause this error, it would really give me some peace of mind. Thanks so much. -Mike Bohan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message