Question on su log

Question on su log

Post by Superus » Sun, 11 Aug 1996 04:00:00



My /usr/adm/sulog is not logging changes to root the way I expect
it should . Instead of showwing users becoming root, it just records
root to root , like:

SU 08/09 16:43 + ttyp0 root-root
SU 08/09 16:47 + tty2A root-news
SU 08/10 11:03 + tty2A root-news
SU 08/10 19:52 + ttyp0 root-root
SU 08/10 22:32 + ttyp0 root-root
SU 08/10 22:50 + ttyp1 root-root

How do I fix this up to record who is becoming root?

Danny Aldham

 
 
 

Question on su log

Post by Stephen Davie » Tue, 13 Aug 1996 04:00:00



> My /usr/adm/sulog is not logging changes to root the way I expect
> it should . Instead of showwing users becoming root, it just records
> root to root , like:

> SU 08/09 16:43 + ttyp0 root-root
> SU 08/09 16:47 + tty2A root-news
> SU 08/10 11:03 + tty2A root-news
> SU 08/10 19:52 + ttyp0 root-root
> SU 08/10 22:32 + ttyp0 root-root
> SU 08/10 22:50 + ttyp1 root-root

> How do I fix this up to record who is becoming root?

> Danny Aldham

We reported this bug to SCO more than 12 months ago.

 
 
 

Question on su log

Post by Bela Lubki » Thu, 15 Aug 1996 04:00:00



> My /usr/adm/sulog is not logging changes to root the way I expect
> it should . Instead of showwing users becoming root, it just records
> root to root , like:

> SU 08/09 16:43 + ttyp0 root-root
> SU 08/09 16:47 + tty2A root-news
> SU 08/10 11:03 + tty2A root-news
> SU 08/10 19:52 + ttyp0 root-root
> SU 08/10 22:32 + ttyp0 root-root
> SU 08/10 22:50 + ttyp1 root-root

> How do I fix this up to record who is becoming root?

This is a known bug in the OSR5 version of su(C), so I guess you're
probably running OSR5.

I've placed a fixed binary on ftp://ftp.sco.com/tmp/su.erg1889.Z.
Checksums are:

  $ sum -r su.erg1889
  44076   106 su.erg1889
  $ md5 su.erg1889
  MD5 (su.erg1889) = 9ec92e66ec555c434623aa8acedc3935

Quote:>Bela<

 
 
 

1. newbie question: logging in as root using the su command

I use Redhat's 5 Linux and I have noticed that I cannot perform the same
tasks after I log in as root, and after I become root using the su command
when I have previously logged in as a normal user.
For example, when I log in as a normal user and then become root using su,
I cannot shutdown/restart my computer. I get the message "shutdown was not
found). In addition I cannot umount a drive (my floppy in particular),
because I get the message that it's busy. I have to exit my normal
account, and then log in as root in order to umount a drive or shutdown my
computer.
Is this the normal procedure? I've read that using su and then shutdown,
should allow me to shutdown my computer. If not which file should I look
into to fix this?
I haven't used my root account for any tasks, except once to add a new
user, so I don't think that I've "damaged" anything...
Thanks in advance for your help.
Nickos

--
to reply remove nospam from my email

2. How to get the volume lable from a mounted CD-ROM

3. su logs?

4. QNX

5. PPP error when only su to root; OK if logged in as root

6. startx won't start!

7. su logging

8. apm resume hangs on IBM T22 with 2.4.19 (harddrive sleeps forever)

9. HELP, users cannot log in and su does not work

10. Can't log in as root, but can su root

11. Can only log into RH as user, "then su -"

12. Digital UNIX and SU Log

13. Unable to log in - no su root possible