Solaris

Hey now!

I am new to Solaris 10 (at least to using Zones on it)

I have just been handed a bunch of servers with zones already created. and I am adding users, setting up .bash_profile and .bashrc scripts.

Does anyone know a way to do things like user adds on all the non-global zones at once? Is this possible? Or do i have to log into each zone as if it were a separate server?

Also, as far as the .bashrc, I know I can propagate it to each user's /home directory, but then I have to do a chown on each one afterward. Is there any way I can place it into the user's /home directory and take on that users ownerships?

I have played around using for loops to reach down into the zones to gather information, as in the for loop below, but executing commands and chowning files adds more complexity than I am comfortable with as far as scripting goes:

# for i in `ls /export/home/zones`
> do
> zlogin $i hostname
> zlogin $i ifconfig -a
> done

thanks in advance!

-Bob

Set-up a NIS or LDAP server and have the accounts created on it.
Set-up an NFS server and have the user's home directories automounted there.

That's it !

If you are adding individual users to individual hosts (ie: not using NIS/LDAP/AD), you should consider adding common home directory files to the skeleton directory. When running useradd, remember that there is a flag to copy the skeleton 'stuff' to the user's home directory.

From "man useradd"

Code:

useradd  [-c comment] [-d dir] [-e expire] [-f inactive]
     [-g group] [-G group [, group...]] [-m [-k skel_dir]]
     [-u uid [-o]] [-s shell] [-A authorization  [,authorization...]]
     [-P profile  [,profile...]] [-R role  [,role...]]
     [-p projname] [-K key=value] login

Look for:

Code:

     -k skel_dir

         A directory that contains skeleton information (such  as
         .profile)  that  can  be  copied  into a new user's home
         directory. This directory must already exist. The system
         provides  the  /etc/skel  directory that can be used for
         this purpose.

     -m

         Create the new user's home  directory  if  it  does  not
         already  exist. If the directory already exists, it must
         have read, write,  and  execute  permissions  by  group,
         where group is the user's primary group.

pick a place for your skeleton directory that you can easily propagate to your various hosts (rsync/nfs/scp), then when you create new users, they will have the common .bashrc file (and others that you identify)

Avronius,

thanks, /etc/skel is a good option for me. One question though. I don't mind if the user owns their .bashrc, but I want root to own .bash_profile upon user creation. If I put .bash_profile into /etc/skel, it will be woned by the user.

I am wondering if I make it a link in /etc/skel will it propagate as a link upon user creation? Or will I cause some damage by putting a link in /etc/skel?

I answered my own question:

# ls -al /etc/skel
total 12
drwxr-xr-x 2 root sys 512 Sep 19 22:24 .
drwxr-xr-x 68 root sys 4608 Sep 18 13:44 ..
lrwxrwxrwx 1 root root 14 Sep 19 22:23 .bash_profile -> /.bash_profile
-rw-r--r-- 1 root root 44 Sep 19 22:24 .bashrc
-rw-r--r-- 1 root other 144 Jan 21 2005 .profile
-rw-r--r-- 1 root sys 136 Jan 21 2005 local.cshrc
-rw-r--r-- 1 root sys 157 Jan 21 2005 local.login
-rw-r--r-- 1 root sys 174 Jan 21 2005 local.profile
# ls -al /export/home/mylogin
total 9
drwxr-xr-x 2 mylogin admin 512 Sep 18 15:04 .
drwxr-xr-x 13 root root 512 Sep 18 13:42 ..
-rw------- 1 mylogin admin 141 Sep 20 10:12 .bash_history
lrwxrwxrwx 1 root root 14 Sep 18 14:02 .bash_profile -> /.bash_profile
-rw-r--r-- 1 root root 44 Sep 18 14:03 .bashrc
-rw-r--r-- 1 mylogin admin 144 Sep 18 13:42 .profile
-rw-r--r-- 1 mylogin admin 136 Sep 18 13:42 local.cshrc
-rw-r--r-- 1 mylogin admin 157 Sep 18 13:42 local.login
-rw-r--r-- 1 mylogin admin 174 Sep 18 13:42 local.profile
#

creating a link inside /etc/skel will create a link in my home directory upon user creation.

oops! Not sure how this is happening, but now whenever I do a useradd, the .bash_profile inder root takes on the ownerships of the user I just created. not a catastrophe, but rather annoying.

I would say what you observe is the expected behavior. The useradd command is doing a chown on the newly created files which propagates to the symlinked root .bash_profile in your special case.

Have a look at line 81 of Cross Reference: /onnv/onnv-gate/usr/src/cmd/oamuser/user/homedir.c