home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!noc.near.net!hri.com!spool.mu.edu!olivea!charnel!rat!zeus!gauss.elee.calpoly.edu!mbelshe
- From: mbelshe@gauss.elee.calpoly.edu (Mike Belshe)
- Newsgroups: comp.unix.ultrix
- Subject: Re: "null" entries in sulog?
- Message-ID: <1993Jan03.084843.197323@zeus.calpoly.edu>
- Date: 3 Jan 93 08:48:43 GMT
- References: <BzxM2q.5Hx@unix.amherst.edu>
- Sender: news@zeus.calpoly.edu
- Organization: CalPoly
- Lines: 33
-
- Tim Pierce writes:
- >Every now and again, I see an entry like the following in
- >/usr/adm/sulog.
- >
- >> SU: /dev/ttyp0 Sat Dec 26 01:47:54 1992
- >
- >Does anyone know what might cause the null username field entry? On a
- >couple of occasions, this has actually appeared as "SU: (null)" (as if
- >a printf statement were passed a char pointer to NULL for the userid).
- >I find this a little worrying, especially as I'm one of the only
- >people on the system who su's in wee hours of the morning and last
- >night I was en route to Boston.
-
- This will happen whenever the user that is executing 'su' is not
- associated with a tty (i.e. not listed in utmp).
-
- I can do this very easily. For example,
- % rsh machineb sh
- su
-
- Now, the rsh runs an 'sh' for me, but does not give me a tty.
- Then, when I execute the su, I will get a "(null)" entry in
- sulog.
-
- Hope this helps,
-
- Mike
- ---
-
- Mike Belshe
- mbelshe@gauss.elee.calpoly.edu
- EL/EE System Administrator
- Cal Poly San Luis Obispo
-