From: zuazaga@ucunix.san.uc.edu (Humberto Ortiz-Zuazaga) Subject: who can't open utmp Date: 13 Feb 1992 16:41:54 GMT
I've got the mylogin3 package up and running on my machine, and it
works. Unfortunately, along with the problems with make and such already
reported, I've run into a problem with the program who, included in the
mylogin3 package.
If I'm logged in as other than root, who fails, reporting
_setutent: Can't open utmp: not owner
Presumably meaning I'm not the owner. I'm not so hot at sysadmin, but
does this have to do with setuid on the binaries? Isn't who supposed to
be able to read utmp no matter whom called it? Whats the fix?
As a related note, kermit reports ENOACCESS errors on /dev/tty65
presumably because it can't open that either because of the permissions.
I guess I have a lot of work to do before I can get other accounts doing
usefull work.
If these are dumb questions, please slap me in the face, then put them
in the FAQ, we're going to need them answered.
-- Humberto Ortiz-Zuazaga INTERNET: zuazaga@ucunix.san.uc.edu Dept. of Physiology & Biophysics BITNET: picone@ucbeh University of Cincinnati CIS: 72301,2303