[comp.unix.xenix.sco] seek error from `w' command

curt@cynic.wimsey.bc.ca (Curt J. Sampson) (03/25/91)

I'm running SCO Xenix 2.3.2 on a 286.  The `w' command gives me a seek
error, though `uptime' works ok.  It is setuid to sysinfo, /dev/kmem
and /dev/swap are both owned and readable by sysinfo, and /xenix and
/etc/utmp are both readable by all.  Does anybody have any clues as to
how to fix this problem?  Thanks.

cjs
-- 
                        | "It is actually a feature of UUCP that the map of
curt@cynic.uucp         | all systems in the network is not known anywhere."
curt@cynic.wimsey.bc.ca |    --Berkeley Mail Reference Manual (Kurt Schoens)

glen@sungate.UUCP (Glen) (03/26/91)

In article <1991Mar25.074823.13361@cynic.wimsey.bc.ca>, curt@cynic.wimsey.bc.ca (Curt J. Sampson) writes:
> I'm running SCO Xenix 2.3.2 on a 286.  The `w' command gives me a seek
> error, though `uptime' works ok.

SCO is aware of the seek error, and they are working on a fix to it; however,
I believe this is a low priority for them and probably will not be addressed
for some time... especially since 2.3.2 is the final release of Xenix-286.

-- 
**  --*--  --*--  --*--  --*--  --*--  --*--  --*--  --*--  --*--  --*--  **
Glen Barney 301-258-5338               It'll take time, but we're going far,
InterNet: glen%sungate@uunet.UU.NET     you and me, I know we are.  In time,
BangPath: uunet!sungate!glen       we'll be dancing in the streets all night

rac@sherpa.UUCP (Roger Cornelius) (03/28/91)

From article <516@sungate.UUCP>, by glen@sungate.UUCP (Glen):
> In article <1991Mar25.074823.13361@cynic.wimsey.bc.ca>, curt@cynic.wimsey.bc.ca (Curt J. Sampson) writes:
>> I'm running SCO Xenix 2.3.2 on a 286.  The `w' command gives me a seek
>> error, though `uptime' works ok.
> 
> SCO is aware of the seek error, and they are working on a fix to it; however,
> I believe this is a low priority for them and probably will not be addressed
> for some time... especially since 2.3.2 is the final release of Xenix-286.

It must be really low priority since I reported this same problem a
year and a half ago when I first upgraded to 2.3.2 on the 286.  I've
since upgraded to SCO UNIX.  uptime/w work correctly there :-).

-- 
Roger A. Cornelius          rac@sherpa.UUCP         uunet!sherpa!rac