"w"(ho) causes "_setutent: Can't open utmp file"

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Jeremy Hartm » Fri, 26 Jan 1996 04:00:00



I have been having the same problem... it seems to be a problem with
the location (??) of the utmp file... under previous version of the
kernel/libraries, the typical location was /etc... I am also not sure
exactly what I changed to affect this... I believe its presumed
location is in files.h, which is set to /etc on my system.. strange..

Help would be much appriciated...

--Jeremy S. Hartman

--http://www.cs.umbc.edu/~jhartm2

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Angus C. Mar » Fri, 26 Jan 1996 04:00:00


I was messing around with my X driver and somehow this strange problem
befell me. When I use "w" (the who command) I get this message:
_setutent: Can't open utmp file: No such file or directory
I don't know how I managed that playing w/X. What do I do about it?

--
                        http://www.ece.concordia.ca/~ac_march/addr.html

 |.........|      |Attempting |
 |: DON'T :|      |recovery...|             Angus March
 |: PANIC :|      |1067 pages |         The Ultra-Mind Dragon
 |:.......:|      |unrecovered|             -==(UDIC)==-
 |---------|___ __|___________|__
/___________\  |_________________| Murphy ain't seen nothing yet

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Jeremy Hartma » Sat, 27 Jan 1996 04:00:00




> >I have been having the same problem... it seems to be a problem with
> >the location (??) of the utmp file... under previous version of the
> >kernel/libraries, the typical location was /etc... I am also not sure
> >exactly what I changed to affect this... I believe its presumed
> >location is in files.h, which is set to /etc on my system.. strange..

> The location should now be /var/run

> --
> Tom Wilson

> http://plains.uwyo.edu/~twilson/homepage.html

Thanks... Problem fixed... now another one has manifested itself... I got
the new procps-.99 and installed it, and now the system (either w or top)
never reports anyone being logged on... weird..

-Jeremy Hartman

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by daniel singh » Sun, 28 Jan 1996 04:00:00


: Thanks... Problem fixed... now another one has manifested itself... I got
: the new procps-.99 and installed it, and now the system (either w or top)
: never reports anyone being logged on... weird..

well, i managed to beat procps-0.99 into compiling too...
my problem is that "w" gives me the people logged in and everything
except whatthey're doing.  that "what" field is always "-", regardless...

does neone have ne idea why?

thxn!

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Terence C Haddoc » Sun, 28 Jan 1996 04:00:00



Quote:> : Thanks... Problem fixed... now another one has manifested itself... I got
> : the new procps-.99 and installed it, and now the system (either w or top)
> : never reports anyone being logged on... weird..

> well, i managed to beat procps-0.99 into compiling too...
> my problem is that "w" gives me the people logged in and everything
> except whatthey're doing.  that "what" field is always "-", regardless...

> does neone have ne idea why?

        I'm having the same problem with w too, and after a long and
arduous search though the source code, I found the problem! W is not
setting the linux version for the proc library, when it attempt to get
the tty numbers from the /proc tree, it's "fixing" a bug in an older
version of Linux by adding 1024 to the device numbers. This causes the
proc library to be unable to get the tty name from the number, and
subsequently causes w not to be able to find any processes owned by a
TTY. to fix this, edit w.c, and add somewhere around line 108 (in main.c,
right after "int maxcmd;":

        set_linux_version().

        And do a 'make w'. This will fix it, and you'll have a fully functioning
w once again.

P.S. I'll send a bug report on this.

Quote:> thxn!

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Lance Kalz » Fri, 02 Feb 1996 04:00:00




: > : Thanks... Problem fixed... now another one has manifested itself... I got
: > : the new procps-.99 and installed it, and now the system (either w or top)
: > : never reports anyone being logged on... weird..
: >
: > well, i managed to beat procps-0.99 into compiling too...
: > my problem is that "w" gives me the people logged in and everything
: > except whatthey're doing.  that "what" field is always "-", regardless...

Hell, procps0.99 won't compile at all because the _Linux_ assembly string
primitives "#include <asm/string.h>" are broken for ELF systems!!  I
refuse to mess with kernel code, so as a result... ARHHGHGHGHGGHGH.  I
_suppose_ there are good reasons not to use the library functions when
running code like this, but right now I can't think of them.  Not for me,
anyway...

Any fixes, anyone?

--
                                Just another lamer in the soup,
                                Lance Kalzus

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Larry Daffn » Sat, 03 Feb 1996 04:00:00





>: > well, i managed to beat procps-0.99 into compiling too...
>: > my problem is that "w" gives me the people logged in and everything
>: > except whatthey're doing.  that "what" field is always "-", regardless...
>Hell, procps0.99 won't compile at all because the _Linux_ assembly string
>primitives "#include <asm/string.h>" are broken for ELF systems!!  I
>refuse to mess with kernel code, so as a result... ARHHGHGHGHGGHGH.  I
>_suppose_ there are good reasons not to use the library functions when
>running code like this, but right now I can't think of them.  Not for me,
>anyway...

I just tossed up a patch for both these problems (and the signames.h
problem) on this very same ng last night.  In fact, our posts probably
passed each other somethime late last night :)  If you miss it or it
gets lost/mangled/folded/spindled/mutilated/turned to windoze drop me
mail and I'll send it to you :)

HTH

-Larry
--

HP Convex Technology Center       | tel: (214)497-4274 / home: (214)380-4382 |
        The great tragedy of science, the slaying of a beautiful
        theory by an ugly fact.  --Thomas Henry Huxley

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Zed C. Pob » Sat, 03 Feb 1996 04:00:00


:
: Hell, procps0.99 won't compile at all because the _Linux_ assembly string
: primitives "#include <asm/string.h>" are broken for ELF systems!!

    This was the simple bug to fix.  Replace <asm/string.h> with
either <linux/string.h> or just <string.h> and you'll be fine.

    My problem is that even with the set_linux_version(); patch w
isn't correctly identifying the online users.  For those users that it
does accidentally get right, it now correctly reports what they're
doing, but it still gives completely inaccurate data sometimes.

=============================================================================

-----------------------------------------------------------------------------

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Harald Koen » Mon, 05 Feb 1996 04:00:00



Quote:> Hell, procps0.99 won't compile at all because the _Linux_ assembly string
> primitives "#include <asm/string.h>" are broken for ELF systems!!  I
> refuse to mess with kernel code, so as a result... ARHHGHGHGHGGHGH.  I
> _suppose_ there are good reasons not to use the library functions when
> running code like this, but right now I can't think of them.  Not for me,
> anyway...

if you don't know how to fix this (simple) problem, you probably shouldn't
run alpha (1.3.*) kernels.  then you wouldn't need to use procps-0.99...
I know this is hard and unfair, but there are lots of good reasons to have
a "production" kernel version (1.2.13 right now).

Harald
--
All SCSI disks will from now on                     ___       _____
be required to send an email notice                0--,|    /OOOOOOO\
24 hours prior to complete hardware failure!      <_/  /  /OOOOOOOOOOO\
                                                    \  \/OOOOOOOOOOOOOOO\
                                                      \ OOOOOOOOOOOOOOOOO|//
Harald Koenig,                                         \/\/\/\/\/\/\/\/\/
Inst.f.Theoret.Astrophysik                              //  /     \\  \

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Mark Trancha » Fri, 09 Feb 1996 04:00:00




> [question about problem deleted]
>if you don't know how to fix this (simple) problem, you probably shouldn't
>run alpha (1.3.*) kernels.  then you wouldn't need to use procps-0.99...
>I know this is hard and unfair, but there are lots of good reasons to have
>a "production" kernel version (1.2.13 right now).

Calling the 1.3.* kernels `alpha' is a little optimistic, isn't it? I've seen
production software that is far less stable than 1.3.48, which I'm running at
the moment!

Mark.

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Mark Trancha » Fri, 09 Feb 1996 04:00:00


Me again. I meant `conservative', not `optimistic'. Sorry.

Mark.

 
 
 

"w"(ho) causes "_setutent: Can't open utmp file"

Post by Zed C. Pob » Sat, 10 Feb 1996 04:00:00



:
:     My problem is that even with the set_linux_version(); patch w
: isn't correctly identifying the online users.  For those users that it

    I found the problem here, too.  Somewhere along the way, something
created a utmp file in /var/run, which w was looking at instead of the
one in /var/log.  I deleted the version in /var/run and made a symlink
to /var/log/utmp and everything worked fine.  "w" is now fully
functional.

=============================================================================

=============================================================================

 
 
 

1. "_setutent: Can't open utmp file: No such file or directory"??

Hi all,

I have Slackware 2.0 installed on my system and upgraded to XFree 3.1
recently without any problem. However, after I upgraded to gcc 2.6.2,
libc-4.6.27, and ld.so.1.5.2, whenever I use xterm, color_xterm, or
even w, message "_setutent: Can't open utmp file: No such file or directory"
appeared. Is there anyway I can fix it??

Thanks,
YH

2. File transfers grind to a halt.

3. _STILL_ get "_setutent: Can't open utmp file.."

4. linux news server

5. USB camera on Blade 100

6. "_setutent: can't open utmp file" after upgrade

7. Three Problems with Red Hat Linux

8. """"""""My SoundBlast 16 pnp isn't up yet""""""""""""

9. "Can't open file" ( flat file ) and "flock()unimplemented ..."

10. GETSERVBYNAME()????????????????????"""""""""""""

11. Strange "w", "who" and "uptime" output

12. quirk: man won't man "w" won't "w" and no telnet