Does anyone have an idea why it is not possible to logon to a newly created user account in Ubuntu 12.04. Is it perhaps a bug with this distro?
On another machine, but running 12.10 there is no such problem.
Accounts have been created with adduser and with GUI. It makes no difference!
The /home owners and the /home/username directories are all both set to the username, but other variations have been tried.
The permissions set are 0740.
Existing accounts which will not allow login and have been deleted with deluser and also with GUI, then new accounts created with different usernames.
Passwords have been successfully changed by sudo passwd. Nothing makes any difference.
This is my final hope before installing 12.10
Code:
Debug log @ 13-01-2014 : 15:42
roy@roy-desktop:~$ sudo adduser --debug ngxxxxx
Adding user `ngxxxxx' ...
Selecting UID from range 1000 to 29999 ...
Selecting GID from range 1000 to 29999 ...
Adding new group `ngxxxxx' (1002) ...
/usr/sbin/groupadd -g 1002 ngxxxxx
Adding new user `ngxxxxx' (1002) with group `ngxxxxx' ...
/usr/sbin/useradd -d /home/ngxxxxx -g ngxxxxx -s /bin/bash -u 1002 ngxxxxx
Creating home directory `/home/ngxxxxx' ...
Copying files from `/etc/skel' ...
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
/usr/bin/chfn ngxxxxx
Changing the user information for ngxxxxx
Enter the new value, or press ENTER for the default
Full Name []: Nxxxx-and-Gxxxxx
Room Number []:
Work Phone []:
Home Phone []:
Other []:
Is the information correct? [Y/n] y
roy@roy-desktop:~$ sudo ls -l /home/ngxxxxx
[sudo] password for roy:
total 12
-rw-r--r-- 1 ngxxxxx ngxxxxx 8445 Jan 13 15:39 examples.desktop
roy@roy-desktop:~$ sudo chmod -R 0740 /home/ngxxxxx
roy@roy-desktop:~$ sudo ls -l /home/ngxxxxx
total 12
-rwxr----- 1 ngxxxxx ngxxxxx 8445 Jan 13 15:39 examples.desktop
I hope somebody has had this problem before - it is most frustrating!!
hi all, i m tryin to create a new account on the unix work station. do i use 'useradd' command? can u guyz advice on the usage of 'useradd' command as it can comes with 'useradd -D' or 'useradd -e'
thanks :confused: (1 Reply)
Hi,
We have a unix user account with login shell as ksh. Now we want to migrate our jobs to a new user account having bash as its login shell.
For the old account we had a .env file which set up a lot of aliases and did a few other useful things. It seems this file was executed the on logging... (2 Replies)
I understand that Unix and it's counterparts are OSs, but would it be possible to just install them to a single user account? I'm using a family computer, whose other users want nothing more complicated on the computer than Internet Explorer, but I want to install Ubuntu so I can easily host my... (6 Replies)
Hello,
I need to install a program that can only be run in unix. I dont have unix on my system. Does anyone know of any free shell accounts with install permissions. I know that there are free shell accounts available on web , but those are without install permission.
Does installing Ubuntu... (7 Replies)
Please help me identify these user accounts..
bin, lp, nuucp, smbnull, mysql, tftp
Can we remove these user or disable these users?We have to apply the security policy about the user identification.Since it was settup by our vendor long time ago. We do not have these informations about these... (3 Replies)
I need to check actual date a user was disabled on my HP-UX server.
Audit is claiming the user account was active during the last audit exercise. (7 Replies)
Discussion started by: cyriac_N
7 Replies
LEARN ABOUT REDHAT
usermod
USERMOD(8) System Manager's Manual USERMOD(8)NAME
usermod - Modify a user account
SYNOPSIS
usermod [-c comment] [-d home_dir [-m]]
[-e expire_date] [-f inactive_time]
[-g initial_group] [-G group [,...]]
[-l login_name] [-p passwd]
[-s shell] [-u uid [-o]] [-L|-U] login
DESCRIPTION
The usermod command modifies the system account files to reflect the changes that are specified on the command line. The options which
apply to the usermod command are:
-c comment
The new value of the user's password file comment field. It is normally modified using the chfn(1) utility.
-d home_dir
The user's new login directory. If the -m option is given the contents of the current home directory will be moved to the new home
directory, which is created if it does not already exist.
-e expire_date
The date on which the user account will be disabled. The date is specified in the format YYYY-MM-DD.
-f inactive_days
The number of days after a password expires until the account is permanently disabled. A value of 0 disables the account as soon as
the password has expired, and a value of -1 disables the feature. The default value is -1.
-g initial_group
The group name or number of the user's new initial login group. The group name must exist. A group number must refer to an already
existing group. The default group number is 1.
-G group,[...]
A list of supplementary groups which the user is also a member of. Each group is separated from the next by a comma, with no inter-
vening whitespace. The groups are subject to the same restrictions as the group given with the -g option. If the user is currently
a member of a group which is not listed, the user will be removed from the group
-l login_name
The name of the user will be changed from login to login_name. Nothing else is changed. In particular, the user's home directory
name should probably be changed to reflect the new login name.
-p passwd
The encrypted password, as returned by crypt(3).
-s shell
The name of the user's new login shell. Setting this field to blank causes the system to select the default login shell.
-u uid The numerical value of the user's ID. This value must be unique, unless the -o option is used. The value must be non-negative.
Values between 0 and 99 are typically reserved for system accounts. Any files which the user owns and which are located in the
directory tree rooted at the user's home directory will have the file user ID changed automatically. Files outside of the user's
home directory must be altered manually.
-L Lock a user's password. This puts a '!' in front of the encrypted password, effectively disabling the password. You can't use this
option with -p or -U.
-U Unlock a user's password. This removes the '!' in front of the encrypted password. You can't use this option with -p or -L.
CAVEATS
usermod will not allow you to change the name of a user who is logged in. You must make certain that the named user is not executing any
processes when this command is being executed if the user's numerical user ID is being changed. You must change the owner of any crontab
files manually. You must change the owner of any at jobs manually. You must make any changes involving NIS on the NIS server.
FILES
/etc/passwd - user account information
/etc/shadow - secure user account information
/etc/group - group information
SEE ALSO chfn(1), chsh(1), passwd(1), crypt(3), groupadd(8), groupdel(8), groupmod(8), useradd(8), userdel(8)AUTHOR
Julianne Frances Haugh (jockgrrl@ix.netcom.com)
USERMOD(8)