03-08-2002
Logging in and then su to root
We have several people that log in using root. What I need to do is have everyone to log in using there own account then su to root. How would I do this. We have aix 4.2
10 More Discussions You Might Find Interesting
1. SuSE
When I try to log on as root now all it does is load YaST. When I used to log on as root it would have a desktop and all...what has happened? Thanks in advance. (10 Replies)
Discussion started by: CTroxtell21
10 Replies
2. UNIX for Dummies Questions & Answers
All,
I want to run a non-root script as the root user with non-root environment variables with crontab. The non-root user would have environment variables for database access such as Oracle or Sybase. The root user does not have the Oracle or Sybase enviroment variables. I thought you could do... (2 Replies)
Discussion started by: bubba112557
2 Replies
3. UNIX for Advanced & Expert Users
Hi everybody, ]
I would like to ask just simpe and short question. I am using freeBSD 6.0 and Debian Sarge.
From Debian console I can log as root using ssh to bsd mashine but not vice versa.
When I say in bsd console su I got sorry output, it does not allow me to su to root when I am logged... (5 Replies)
Discussion started by: 100days
5 Replies
4. AIX
Hi, yesterday, I changed root's shell in /etc/passwd, cause a mistake then I can not log in root account (can't find correct shell). I attempted to log in single-mode, however, it prompted for single-mode's password then I type root's password but still can not log in.
I'm using AIX 5L version 5.2... (2 Replies)
Discussion started by: neikel
2 Replies
5. Solaris
I would like to know how to prevent users connecting to a server using SSH as root.
I would still like them to be able to login with their username and then change to su.
But I would like to prevent them logging in directly as root.
I have searched the forum and read that I should set... (3 Replies)
Discussion started by: Sepia
3 Replies
6. HP-UX
when i am trying to login through root i am getting following error
Last successful login for root: Tue Feb 3 16:44:40 IST-5:30 2009 on pts/tc
Last unsuccessful login for root: Tue Feb 3 16:41:01 IST-5:30 2009 on pts/tc
Please wait...checking for disk quotas
crt0: ERROR couldn't open... (6 Replies)
Discussion started by: mnmca
6 Replies
7. Post Here to Contact Site Administrators and Moderators
Hi Everyone. First, I want to thank all of you for letting me participate in this great group.
I am having a bit of a problem.
After I get an email from a responder, I login to make my reply.
In the mean time I get another response by email from another member, I go to reply to them and I... (6 Replies)
Discussion started by: Ccccc
6 Replies
8. UNIX for Dummies Questions & Answers
I have created a linux machine and installed some softwares on it with root user privileges . I used to login with root user credentials for doing the various task.
Later i have realise that this is not the best practice to follow and there should be a new user with less privileges to be created... (1 Reply)
Discussion started by: pinga123
1 Replies
9. Solaris
Hi All
After downloading ZFS documentation from oracle site, I am able to successfully migrate UFS root FS without zones to ZFS root FS. But in case of UFS root file system with zones , I am successfully able to migrate global zone to zfs root file system but zone are still in UFS root file... (2 Replies)
Discussion started by: sb200
2 Replies
10. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
LEARN ABOUT CENTOS
pam_lastlog
PAM_LASTLOG(8) Linux-PAM Manual PAM_LASTLOG(8)
NAME
pam_lastlog - PAM module to display date of last login and perform inactive account lock out
SYNOPSIS
pam_lastlog.so [debug] [silent] [never] [nodate] [nohost] [noterm] [nowtmp] [noupdate] [showfailed] [inactive=<days>]
DESCRIPTION
pam_lastlog is a PAM module to display a line of information about the last login of the user. In addition, the module maintains the
/var/log/lastlog file.
Some applications may perform this function themselves. In such cases, this module is not necessary.
If the module is called in the auth or account phase, the accounts that were not used recently enough will be disallowed to log in. The
check is not performed for the root account so the root is never locked out.
OPTIONS
debug
Print debug information.
silent
Don't inform the user about any previous login, just update the /var/log/lastlog file.
never
If the /var/log/lastlog file does not contain any old entries for the user, indicate that the user has never previously logged in with
a welcome message.
nodate
Don't display the date of the last login.
noterm
Don't display the terminal name on which the last login was attempted.
nohost
Don't indicate from which host the last login was attempted.
nowtmp
Don't update the wtmp entry.
noupdate
Don't update any file.
showfailed
Display number of failed login attempts and the date of the last failed attempt from btmp. The date is not displayed when nodate is
specified.
inactive=<days>
This option is specific for the auth or account phase. It specifies the number of days after the last login of the user when the user
will be locked out by the module. The default value is 90.
MODULE TYPES PROVIDED
The auth and account module type allows to lock out users which did not login recently enough. The session module type is provided for
displaying the information about the last login and/or updating the lastlog and wtmp files.
RETURN VALUES
PAM_SUCCESS
Everything was successful.
PAM_SERVICE_ERR
Internal service module error.
PAM_USER_UNKNOWN
User not known.
PAM_AUTH_ERR
User locked out in the auth or account phase due to inactivity.
PAM_IGNORE
There was an error during reading the lastlog file in the auth or account phase and thus inactivity of the user cannot be determined.
EXAMPLES
Add the following line to /etc/pam.d/login to display the last login time of an user:
session required pam_lastlog.so nowtmp
To reject the user if he did not login during the previous 50 days the following line can be used:
auth required pam_lastlog.so inactive=50
FILES
/var/log/lastlog
Lastlog logging file
SEE ALSO
pam.conf(5), pam.d(5), pam(8)
AUTHOR
pam_lastlog was written by Andrew G. Morgan <morgan@kernel.org>.
Inactive account lock out added by Toma Mraz <tm@t8m.info>.
Linux-PAM Manual 09/19/2013 PAM_LASTLOG(8)