Hi Sun Managers:
I had received two "me-toos" so I contacted SUN to help me with
the useradd problem (see original question below). Their solution
was:
Use "passwd -d" to delete the password lock (*LK*) from
/etc/shadow after creating the user account
# useradd -u 1001 -g 1000 -d /h/sysop/vlau -m -k /etc/skel/local \
-s /bin/csh -c "Vicky Lau" -f 180 vlau >& /dev/null
# passwd -d vlau
=========================================================================
Original question:
==================
I've been testing out the Sun's command line interface "useradd"
to add new users to each local system running Solaris 2.3 without
NIS. This will be integrated into some csh script to automate
password aging. I created a new user with the following lines:
# useradd -u 1001 -g 1000 -d /h/sysop/vlau -m -k /etc/skel/local \
-s /bin/csh -c "Vicky Lau" -f 180 vlau >& /dev/null
# passwd vlau
XXX
When the user vlau logged in to the system with the correct password,
the following sequence occurred:
Password:(CORRECT PASSWORD ENTERED)
Login incorrect
But if I create the same account with a much simpler useradd line,
log in as the user, run userdel to delete the newly created
account, resubmit the desired useradd line, then the user can log in:
# useradd -u 1001 -g 1000 vlau
# passwd vlau
XXX
Log in as vlau with success
Log off
# useradd -u 1001 -g 1000 -d /h/sysop/vlau -m -k /etc/skel/local \
-s /bin/csh -c "Vicky Lau" -f 180 vlau >& /dev/null
# passwd vlau
XXX
User is able to log in
I checked the /etc/passwd and /etc/shadow files and compared them during
the above two sessions. They look OK to me. "passwd -s vlau" shows a
PS status. Could there be some other files or protection I've overlooked?
=========================================================================
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:26 CDT