Error: _setutent: Can't open utmp file: ... ???

Error: _setutent: Can't open utmp file: ... ???

Post by Anders Kristens » Tue, 31 Jan 1995 22:42:08



After having upgraded my Linux kernel from 1.0 to 1.1.78 I keep
getting anoying error messages from new shells:

  _setutent: Can't open utmp files: no such file or directory

Now, the file /etc/utmp does exist. It is owned by root and belongs
to user group root. It has the following permissions: -rw-r--r--.

Does anyone have a clue what this is about ???

Cheers,
Anders
--
------------------------------------------------------------
  Anders Kristensen             Hewlett-Packard Laboratories

  Phone: +44 272 228164         Stoke Gifford
  Fax:   +44 272 228003         BS12 6QZ
  Telnet: 31 28164              England
------------------------------------------------------------

 
 
 

Error: _setutent: Can't open utmp file: ... ???

Post by David Mey » Wed, 01 Feb 1995 04:59:12




>After having upgraded my Linux kernel from 1.0 to 1.1.78 I keep
>getting anoying error messages from new shells:

>  _setutent: Can't open utmp files: no such file or directory

>Now, the file /etc/utmp does exist. It is owned by root and belongs
>to user group root. It has the following permissions: -rw-r--r--.

>Does anyone have a clue what this is about ???

No, but I get the same thing.  Unfortunately, I have no idea what the
actual cause is, since I upgraded libc, gcc, ld, and the kernel at the
same time.  I haven't bothered to try downgrading each to see who the
culprit is because it would be such a pain, but I suspect libc.

                Dave
--
David M. Meyer                             Mechanical & Aerospace Engineering

NeXTmail ok

 
 
 

Error: _setutent: Can't open utmp file: ... ???

Post by H.P.Heiding » Wed, 01 Feb 1995 09:23:33



# After having upgraded my Linux kernel from 1.0 to 1.1.78 I keep
# getting anoying error messages from new shells:
#
#   _setutent: Can't open utmp files: no such file or directory
#
# Now, the file /etc/utmp does exist. It is owned by root and belongs
# to user group root. It has the following permissions: -rw-r--r--.
#
# Does anyone have a clue what this is about ???

  Look at /usr/include/paths.h, which defines:

        /* <- I commented it out since I have a separate root-filesystem ...
        #if 0
        #define _PATH_UTMP      "/etc/utmp"
        #else
        #define _PATH_UTMP      "/var/adm/utmp"
        #endif
        */

        #define _PATH_UTMP      "/etc/utmp"  /* ... and defined this, though */
        #define _PATH_WTMP      "/var/adm/wtmp"
        #define _PATH_LASTLOG   "/var/adm/lastlog"
        #define _PATH_LOCALE    "/usr/lib/locale"
        #define _PATH_RWHODIR   "/var/spool/rwho"

  Best is, you place a symlink /var/adm/utmp -> /etc/utmp; i.e.:

         ln -s /etc/utmp /var/adm/utmp

  Due to the definition, sys-calls that access the utmp-file look for
  it in /var/adm/.. after you compiled a fresh kernel. But probably
  older applications look for it in /etc/..

#   Anders Kristensen             Hewlett-Packard Laboratories

Regards, Peter
--
#--------- H.P. Heidinger, Steeler Str. 121, 45138 Essen /Germany ----------#

# A supercomputer is a machine, that runs an endless loop in just 2 seconds #

 
 
 

1. Error:_setutent: Can't open utmp file -- how to fix?

I saw someone else with this error in the last month or so, but never
did see an answer.  Whenever I use "w" or bring up an xterm window,
I get the following error:

_setutent: Can't open utmp file: No such file or directory

/etc/utmp is there, is owned by root, and has permissions 644.

This simply stopped working over the last two days.. at least I have
*no* idea what I could've done that might have changed it.  I added
nothing new to the system, and didn't change any system files...

Reboot has no effect.

Any help would be appreciated.

Sean.

---
Sean L. Gilley                             The Information Super Highway is
614-860-9053 (h), 614-860-5743 (w)         really a rough gravel road with

2. IE bug - with mod_rewrite?!

3. Error: _setutent: Can't open utmp file:

4. Authentication Times

5. ERROR: _setutent: Can't open utmp file.....

6. FreeBSD as host for embedded development?

7. _setutent: Can't open utmp file: No such file or directory

8. Ethernet config/detection problems

9. _setutent Can't open utmp file: No such file or directory

10. _setutent: Cant'open utmp file:No such file or directory

11. _setutent: Can't open utmp file: No such file or directory

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