08-02-2005
root login problem in cde
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have Sun Netra X1 Server which is headless means no CDROM, no terminal etc. I am connected it through serial port.
Accidently, someone in our department changed the root's default shell to /sbin/tcsh while there is no tcsh in /sbin and he logs off. Now, I am trying to logon as root on system... (2 Replies)
Discussion started by: s_aamir
2 Replies
2. HP-UX
Hi All,
I m facing a problem that, i m not able to login as root user on cde on hp-ux 11.00, i can login as root on commond line as well as telnet. Thanks in Advance for help.
Regards,
Awadhesh (1 Reply)
Discussion started by: Awadhesh
1 Replies
3. UNIX for Advanced & Expert Users
I'm having problem with the CDE pre login banner.
I configured the c/usr/dt/config/C/Xresources file to add my warning message:
Dtlogin*greeting.labelString: My Banner
I then modified the Dtlogin*greeting*fontList to display the message in smaller text. This did not work.
... (1 Reply)
Discussion started by: equismorio
1 Replies
4. Solaris
Dear All
I am in a strange situation where I have install the Solaris 10 5/08 OS on Netra 1280 server. When I connect it through my laptop so that I can take the GUI from xmanager. When I try to login as root or any other users also through Java Destop Environment which accepted it after few... (3 Replies)
Discussion started by: girish.batra
3 Replies
5. HP-UX
Dear Forum,
I had this problem initially with HPUX 11.23, all users including root could not login via CDE or telnet. Then after some workarounds, it resolved by resetting root password via console login. After enabling back all users to login normally (via CDE or telnet), only root can not... (4 Replies)
Discussion started by: irda
4 Replies
6. AIX
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
I... (0 Replies)
Discussion started by: semso
0 Replies
7. UNIX for Dummies Questions & Answers
Hi, can somebody please, please help me?
After a power loss and server restart my server running AIX 4.2.2 could not boot. Following the procedure in my user guide
I checked the hd's with
# fsck -y /dev/hd1
# fsck -y /dev/hd2
# fsck -y /dev/hd3
# fsck -y /dev/hd4
# fsck -y /dev/hd9var
... (4 Replies)
Discussion started by: semso
4 Replies
8. UNIX for Advanced & Expert Users
Hello,
I created a user in my AIX 5.3 system and i modified /etc/passwd file in and assigned this user the uid=0 like root user.
The problem is that when this user log into the system through putty it asks for root password instead of the user password.
As a result of this, if i reset the... (4 Replies)
Discussion started by: omonoiatis9
4 Replies
9. Solaris
Hi,
we have instaled Solaris 10 on a SUN V490, installation went okay but now when I type “root” and press return it comes back with the “Login incorrect” without ever asking for a password... (6 Replies)
Discussion started by: manni2
6 Replies
LEARN ABOUT DEBIAN
calife
CALIFE(1) BSD General Commands Manual CALIFE(1)
NAME
calife -- becomes root (or another user) legally.
SYNOPSIS
calife [-] [login]
or
... [-] [login] for some sites (check with your administrator).
DESCRIPTION
Calife requests user's own password for becoming login (or root, if no login is provided), and switches to that user and group ID after veri-
fying proper rights to do so. A shell is then executed. If calife is executed by root, no password is requested and a shell with the appro-
priate user ID is executed.
The invoked shell is the user's own except when a shell is specified in the configuration file calife.auth.
If ``-'' is specified on the command line, user's profile files are read as if it was a login shell.
This is not the traditional behavior of su.
Only users specified in calife.auth can use calife to become another one with this method.
You can specify in the calife.auth file the list of logins allowed for users when using calife. See calife.auth(5) for more details.
calife.auth is installed as /etc/calife.auth.
FILES
/etc/calife.auth List of users authorized to use calife and the users they can become.
/etc/calife.out This script is executed just after getting out of calife.
SEE ALSO
su(1), calife.auth(5), group(5), environ(7)
ENVIRONMENT
The original environment is kept. This is not a security problem as you have to be yourself at login (i.e. it does not have the same security
implications as in su(1) ).
Environment variables used by calife:
HOME Default home directory of real user ID.
PATH Default search path of real user ID unless modified as specified above.
TERM Provides terminal type which may be retained for the substituted user ID.
USER The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root).
BUGS
The MD5-based crypt(3) function is slower and probably stronger than the DES-based one but it is usable only among FreeBSD 2.0+ systems.
HISTORY
A calife command appeared in DG/UX, written for Antenne 2 in 1991. It has evolved considerably since this period with more OS support, user
lists handling and improved logging.
PAM support was introduced in 2005 to port it to MacOS X variants (Panther and up).
AUTHOR
Ollivier Robert <roberto@keltia.freenix.fr>
BSD
September 25, 1994 BSD