Sponsored Content
Operating Systems Solaris Unable to login as a User or Root on one client Post 302299312 by deaconf19 on Thursday 19th of March 2009 09:37:18 PM
Old 03-19-2009
The pwconv command I could not use since the shadow file is missing entirely and the single user mode is not working. Unless I am looking at this command the wrong way
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Other than root user .Normal user is unable to create files

Hi all, I am using Sun Solaris 9 .In this system normal users unable to create files from the command line.I added these users in bin,adm and even root group i found them unable to create a file. (1 Reply)
Discussion started by: mallesh
1 Replies

2. UNIX for Advanced & Expert Users

unable to change user password from nis client

I trying to change the user1 passwd from NIS client i.e #passwd -r nis user1 Enter user1's password; Can I change the password without having to enter user password? Mnay Thanks (1 Reply)
Discussion started by: sam786
1 Replies

3. Solaris

Am not able to login as a root User with telnet

Hi to All, I have configured telnet service in my server but am not able to login with root user in Linux Servers. For that what can i do ? Please help me Thanks in Advance. (1 Reply)
Discussion started by: Sharath Kumar
1 Replies

4. Linux

Unable to login with root for more than 2 sessions

Hi, I am unable to login with root for more than 2 sessions. Plz help any thing need to updated? Suresh (2 Replies)
Discussion started by: suresh3566
2 Replies

5. UNIX for Dummies Questions & Answers

Can not login with root user

Hi folks. our developer had a root user and he changed some settings about root user. We have not known what he changed. There is an oracle user, we can login to oracle, no problem. But when we try to login to root user we are getting this error : $ su root Password: bash:... (9 Replies)
Discussion started by: futi
9 Replies

6. Shell Programming and Scripting

login as root user

hello all, if we haven't set a password to root user, how can we login as root user in konsole by using su? is it necessary to set password for root to login as root user?how can we set password to root user? (6 Replies)
Discussion started by: aarathy
6 Replies

7. Solaris

Unable to switch back to root from user

Hi, I am new to Solaris and when i am trying to Switch to root login from user, system throws message saying permissions denied... Steps I Followed: Created a user and logged into that user by SU username tried to come back to root but system throws message "permissions denied" ... (7 Replies)
Discussion started by: VijaySolaris
7 Replies

8. Shell Programming and Scripting

How to Login as another user through Shell script from current user[Not Root]

Hi Every body, I would need a shell script program to login as different user and perform some copy commands in the script. example: Supppose ora_toms is the active user ora_toms should be able to run a script where user: ftptomsp pass: XXX should login through and run the commands ... (9 Replies)
Discussion started by: ujjwal27
9 Replies

9. Solaris

Unable to login with any user

Hi Please I need help on trying to login on a solaris 10, blade server. login as: root Using keyboard-interactive authentication. Password: I even try a normal user, I do not get the prompt. I suspect the reason could be that /varis at 98% because I have configure email alerts to warn me... (9 Replies)
Discussion started by: fretagi
9 Replies

10. UNIX for Dummies Questions & Answers

Unable to change password using root user

Hi, I tired changing password for mqm user in linux server with root user. But still I couldn't able to login mqm user with changed password. Can anyone please help on this. # passwd mqm Thanks, Anusha (4 Replies)
Discussion started by: Anusha M
4 Replies
RLOGIND(8)						      System Manager's Manual							RLOGIND(8)

NAME
rlogind, in.rld - remote login server SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld tcpd login /usr/sbin/in.rld DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port numbers from trusted hosts. Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). When a service request is received the following protocol is initiated: 1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection. 2) The server checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used. Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line. The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from the client, and window size changes from the client are propagated to the pseudo terminal. SEE ALSO
rlogin(1). DIAGNOSTICS
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An error is indicated by a leading byte with a value of 1. ``Try again.'' A fork by the server failed. ``/bin/sh: ...'' The user's login shell could not be started. BUGS
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is useful in an ``open'' environment. A facility to allow all data exchanges to be encrypted should be present. A more extensible protocol should be used. 4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)
All times are GMT -4. The time now is 11:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy