Bug 27798

Summary: /usr/bin/w cannot format the output correctly
Product: Base System Reporter: jhluo <jhluo>
Component: binAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description jhluo 2001-05-31 19:10:01 UTC 
When someone's process name or host name longer than certain bytes,
the w/uptime can't format correctly and gerenates an output:
Note that two users are missed in the list since "No such file or directory"

w: /dev/a;ttyp: No such file or directory
w: /dev/ar: No such file or directory
 1:42AM  up 26 mins, 5 users, load averages: 0.03, 0.06, 0.06
USER             TTY      FROM              LOGIN@  IDLE WHAT
sob              pb       ccsun32.cc.nctu.  1:35AM     - bbs absolt /dev/ttypb
av               P4       Nerv.Dorm-GD2.NC  1:23AM     - w
sob              P7       ccsun34.cc.nctu.  1:41AM     - -

Fix: 

data sorting problem?
How-To-Repeat: Login with long long hostnames
Comment 1 dima 2001-05-31 23:02:04 UTC 
jhluo@kimo.com.tw writes:
> 
> >Number:         27798
> >Category:       bin
> >Synopsis:       /usr/bin/w cannot format the output correctly
> >Description:
> When someone's process name or host name longer than certain bytes,
> the w/uptime can't format correctly and gerenates an output:
> Note that two users are missed in the list since "No such file or directory"
> 
> w: /dev/a;ttyp: No such file or directory
> w: /dev/ar: No such file or directory
>  1:42AM  up 26 mins, 5 users, load averages: 0.03, 0.06, 0.06
> USER             TTY      FROM              LOGIN@  IDLE WHAT
> sob              pb       ccsun32.cc.nctu.  1:35AM     - bbs absolt /dev/ttypb
> av               P4       Nerv.Dorm-GD2.NC  1:23AM     - w
> sob              P7       ccsun34.cc.nctu.  1:41AM     - -
> 
> >How-To-Repeat:
> Login with long long hostnames

This isn't very helpful.  Login using what (ssh, telnet, etc.)?  How
long of a hostname?

> 
> >Fix:
> data sorting problem?
> >Release-Note:
> >Audit-Trail:
> >Unformatted:
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-bugs" in the body of the message
>
Comment 2 dd freebsd_committer freebsd_triage 2001-06-02 03:49:32 UTC 
State Changed
From-To: open->closed

Originator reports that this isn't a FreeBSD problem.