Sponsored Content
Contact Us Forum Support Area for Unregistered Users & Account Problems [SOLVED] matrixmadhan - login problem Post 302704515 by Neo on Friday 21st of September 2012 11:55:14 PM
Old 09-22-2012
In the future, you can also try the link to the Lost Password Recovery function.
 

9 More Discussions You Might Find Interesting

1. Programming

matrixmadhan,please come on in

Hi, I ' m a graduate , and now I have to choose a graduation design, I really want to choose one about UNIX , so what I want is to get some advice from you, could you suggest me what I can do ? what I major is computer science and just know a little about UNIX,but I am so interested in it,and I... (2 Replies)
Discussion started by: blf0
2 Replies

2. AIX

user login problem & Files listing problem.

1) when user login to the server the session got colosed. How will resolve? 2) While firing the command ls -l we are not able to see the any files in the director. but over all view the file system using the command df -g it is showing 91% used. what will be the problem? Thanks in advance. (1 Reply)
Discussion started by: pernasivam
1 Replies

3. AIX

Problem Solved

Generally, most people, I guess, go from 5.3 ML4 Directly to TL 7. So they may never run into this issue. For the rest of us, here is the resolution of my problem in going from ML6 to TL7. Apparently with the change from ML to TL IBM added a "BuildDate Verification" routine into... (1 Reply)
Discussion started by: mrmurdock
1 Replies

4. Solaris

[Solved] Solaris 10 - Ftp Login incorrect

Hey everyone, I am trying to get a 2GB patch cluster FTP'd to a solaris 10 server. I have tried logging in via ftp, and both with root as well as my personal account, I get "Login Incorrect." I have verified that I can log in using telnet. -bash-3.00$ netstat -a |grep ftp *.ftp ... (10 Replies)
Discussion started by: msarro
10 Replies

5. Solaris

[Solved] How to change my default login mode????

Hi guys, I have just installed Solaris 10 x86. My system boots into graphical login by default, I want to have text login only, where can I change that. I tried to use the linux and bsd concept of editing /etc/inittab, and change the default value to 3, but that doesn't work in Solaris. Please... (6 Replies)
Discussion started by: gabam
6 Replies

6. HP-UX

[Solved] root cannot login

Dear all, cannot login to a HP unix server using root as well as other logins. Even root also cannot enter. It seems that they have changed some permissions in / Any way of recovering the system or getting logged in . Thanks in advance Rj (8 Replies)
Discussion started by: jegaraman
8 Replies

7. SuSE

[Solved] Last Login Log

Hello again I am using SLES Enterprise 9, and 10 and I was hoping I could implement a user login logs like how medusa does for HP-UX. Is there an equivalent tool for Linux? I am heavily depended on /var/log/lastlog and last commands but surely there must be something more out there. Or if... (3 Replies)
Discussion started by: hedkandi
3 Replies

8. UNIX for Dummies Questions & Answers

login profile[solved]

i vi .profile Set DATE `date +%m%d%Y%H%M`, but after logout/login, echo $DATE, it shows: Fri Mar 23 15:01:53 EDT 2012, i want to show: 032320121501 please ignore. vi /etc/profile, and export DATE=`date +%m%d%Y%H%M`, worked fine now. (0 Replies)
Discussion started by: lawsongeek
0 Replies

9. Solaris

[solved] Ssh passwordless login not working

This is Solaris 10 and sorce+destination are non root user. Somehow it is broke and I am not able to fix it. Already checked permissions on both servers and authorized_keys entry of destination is same as id_rsa.pub of source server. I can not regenerate keys on source server because I do not know,... (0 Replies)
Discussion started by: solaris_1977
0 Replies
PASSWD(5)							   File formats 							 PASSWD(5)

NAME
passwd - password file DESCRIPTION
Passwd is a text file, that contains a list of the system's accounts, giving for each account some useful information like user ID, group ID, home directory, shell, etc. Often, it also contains the encrypted passwords for each account. It should have general read permission (many utilities, like ls(1) use it to map user IDs to user names), but write access only for the superuser. In the good old days there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the hardware was too slow to crack a well-chosen password, and moreover, the basic assumption used to be that of a friendly user-community. These days many people run some version of the shadow password suite, where /etc/passwd has *'s instead of encrypted passwords, and the encrypted passwords are in /etc/shadow which is readable by the superuser only. Regardless of whether shadow passwords are used, many sysadmins use a star in the encrypted password field to make sure that this user can not authenticate him- or herself using a password. (But see the Notes below.) If you create a new login, first put a star in the password field, then use passwd(1) to set it. There is one entry per line, and each line has the format: account:password:UID:GID:GECOS:directory:shell The field descriptions are: account the name of the user on the system. It should not contain capital letters. password the encrypted user password or a star. UID the numerical user ID. GID the numerical primary group ID for this user. GECOS This field is optional and only used for informational purposes. Usually, it contains the full user name. GECOS means General Electric Comprehensive Operating System, which has been renamed to GCOS when GE's large systems division was sold to Honeywell. Dennis Ritchie has reported: "Sometimes we sent printer output or batch jobs to the GCOS machine. The gcos field in the password file was a place to stash the information for the $IDENTcard. Not elegant." directory the user's $HOME directory. shell the program to run at login (if empty, use /bin/sh). If set to a non-existing executable, the user will be unable to login through login(1). NOTE
If you want to create user groups, their GIDs must be equal and there must be an entry in /etc/group, or no group will exist. If the encrypted password is set to a star, the user will be unable to login using login(1), but may still login using rlogin(1), run existing processes and initiate new ones through rsh(1), cron(1), at(1), or mail filters, etc. Trying to lock an account by simply chang- ing the shell field yields the same result and additionally allows the use of su(1). FILES
/etc/passwd SEE ALSO
passwd(1), login(1), su(1), group(5), shadow(5) 1998-01-05 PASSWD(5)
All times are GMT -4. The time now is 08:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy