Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I created some users with:

$ useradd john

and I forgot to specify the parameter -m to create the home directory and to have the skeleton files copied to each user. now I want to do that, and I don't want to recreate all users (there must be an easier way). so, is there any way to create the user directories and copy the skeleton files?

I thought about creating the directories, chowning them to the corresponding user, copying all the skeleton files and chowning them to the corresponding user. but if there's a command like useradd -m that doesn't create the user again, but create the directories, it'd be better.

share|improve this question
    
Did this happen with a large list of users? –  David Rickman Sep 9 '09 at 15:04
    
I had around 10 users with this problem. –  CD1 Sep 9 '09 at 19:35

9 Answers 9

up vote 9 down vote accepted

This might sound like a silly idea, but if the users aren't actually doing anything, you could do:

cat /etc/passwd | cut -f 1 -d : >/tmp/users.list

Then edit /tmp/users.list to only contain the users you want. Then do:


for i in `cat /tmp/users.list`
do
    userdel $i
    useradd -m $i
done

However, many Redhat based distributions will create you a new home directory when you first login, providing it is specified in /etc/passwd where the directory should be.

To test that, do an "su - " and see if it does "the right thing". If it doesn't, the above script will work quite nicely, I think.

share|improve this answer
1  
yes, it worked, although it created new UIDs and GIDs (but that wasn't a problem). but I forgot to backup the passwords from /etc/shadow, now the users will have to set their passwords again =/ –  CD1 Sep 9 '09 at 15:18
    
If he created them recently he might be able to do: cat /etc/passwd | egrep '^\:[0-9]{4}\:' | cut -f 1 -d : >/tmp/users.list That should only grab UID of valid users, and not system users. –  David Rickman Sep 9 '09 at 15:18
    
What about passwords, do they remain the same? I fear not! –  math May 12 '12 at 15:57
    
for i in $(awk -F: '{print $1 }' /etc/passwd) –  Rahul Patil Jul 9 '13 at 6:48
    
why use grep or cut with cat and with pipe, why not directly in this way? cut -f 1 -d : < /etc/passwd > passwtmp –  c4f4t0r Dec 12 '13 at 12:01

Also you can use mkhomedir_helper

Usage: /sbin/mkhomedir_helper <username> [<umask> [<skeldir>]]
share|improve this answer
2  
This is the only answer that actually answers the question without some 10 line script. –  Brendan Byrd Jan 6 at 23:58
    
Simple. Thanks! –  mawaldne Jan 8 at 19:24
    
This and the pam answer are the best here, thanks. Never mess with those files by hand if you can avoid it. –  h4unt3r Jan 21 at 1:02

You will need to create the users directory manually. This requires three steps:

  1. Create directory in compliance to /etc/passwd, usually there will be already a /home/login entry.
  2. Copy initial files from /etc/skel
  3. And finally set right permissions:

    • mkdir /home/YOU
    • cd /home/YOU
    • cp -r /etc/skel/.* /etc/skel/* .
    • chown -R YOU.YOURGROUP .
    • chmod -R go=u,go-w .
    • chmod go= .

BTW: I always miss the -m option for useradd too. At least Debian based systems should have an adduser command, which I recommend over useradd. If you missed -m option it might also be worth considering to deluser and then recreate the user with proper options.

Edit: Added -r for copying also directories.

share|improve this answer
    
Did that: usernameh=myusername; mkdir /home/$usernameh ; cp /etc/skel/* /etc/skel/.* /home/$usernameh; chown -R $usernameh:$usernameh /home/$usernameh; chmod -R 755 /home/$usernameh; –  Aki Sep 26 '13 at 15:11
    
Personally I don't like the 755 chmod, as it allows users to spy into other users home's. I think each user should explicitly grant access to others. As public_html needs at least x bit set, I would recommend chmod 0711 on each home, public_html and similar directories as default. –  math Sep 27 '13 at 7:51
    
also, use cp -r for skel, as else it won't copy directories (.ssh). –  Aki Sep 27 '13 at 12:22
    
On my system (Arch Linux on ARM) cp -r /etc/skel/.* recurse back into /etc/ and copies all data from here (/etc/skel/.* matches /etc/skel/.. I expect). The solution from superuser.com/a/61619/22153 seem to work: cp -r /etc/skel /home/user (/home/user must not exist before running the command) –  zpon 14 hours ago

You can use something like pam_mkhomedir to prevent this from ever being an issue with any users in the future. pam_mkhomedir is a PAM module that automatically creates a user's home directory on login if it doesn't exist, and populates it with files from /etc/skel (or whatever skel directory you specify).

This is also a nicely scalable approach because it will continue to solve this problem if you ever switch your user repository over to a directory service like LDAP in the future.

share|improve this answer
mkdir -p /home/john
chown john:john /home/john
usermod -d /home/john john

That should do the trick I believe

share|improve this answer
2  
it says: usermod: no changes. and the directory isn't created. it doesn't work either with the -m option. –  CD1 Sep 9 '09 at 14:56
1  
Alright. I figured out why that didn't work, useradd used to only put $HOME_DIR in /home unless you specified otherwise. It now seems to automatically put it in /home/$USER instead. A cheap way might be to usermod -d /home/john2 -m john then run usermod -d /home/john -m. –  David Rickman Sep 9 '09 at 15:09
    
Nevermind that doesn't work either. –  David Rickman Sep 9 '09 at 15:10
1  
Well at least you learned something new. –  David Rickman Sep 9 '09 at 15:38
1  
You forgot to copy the contents of /etc/skel/ + chown recursive for those new files. usermod wouldn't work since here the directory was registered but not created, usermod won't do anything. –  Aki Sep 26 '13 at 15:12

In my case, the home volume was corrupted and I decided just rebuild it from scratch since not much data involved but I want to keep users' login information, so I recreated the home directories manually with this script:

#!/bin/bash
cat /etc/passwd | while IFS=: read n x i g c d r
do
  # my system has uid started at 1000, but has nfsnobody at 65534:
  if [[ "$i" -ge 1000 && "$i" -le 65000 && ! -x "$d" ]]
  then
    cp -av /etc/skel "$d"
    chown -R "$i:$g" "$d"
    # may needed in SELinux system:
    restorecon -R "$d"
    # add your chmod as your need:
    chmod -R o-rw "$d"
  fi
done
share|improve this answer

If you edit /etc/login.defs to contain

CREATE_HOME yes

then home directories will be automatically created for any future users, unless you tell the system not to do so.

Another option is to use PAM for logins, and use the pam_mkhomedir module to automagically create the homedir on the first login.

share|improve this answer

My first step after doing a useradd is to su - <user>.

Creates the home directories, copies skeletons, etc - at least on the CentOS 4 box I do that on most frequently.

share|improve this answer

You could simply edit /etc/passwd. The second to the last field is the user's home directory.

greeblesnort:x:1000:1000:greeblesnort,,,:/home/greeblesnort:/bin/bash
share|improve this answer
    
They users were already created. The home directories weren't created because he forgot a switch. –  David Rickman Sep 9 '09 at 19:27
    
I didn't mean to change the user's home directory, I meant to create the directory and copy the skeleton files to it with the appropriate permissions after the user has been added. –  CD1 Sep 9 '09 at 19:37

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.