Get APLawrence.com by RSSA simple script for adding SCO users
By Dirk HartAdanac Software
Email: dhart@mailstarusa.com
Web Site: MailStarUSA.com
One day I was adding a user to my customers system - I must have been tired - I had forgotten one of the steps and had wasted about an hour figuring it out. Frustrated, I muttered to myself 'There *must* be a better way!'.
Well, with unix hard stuff can often be easy: I wrote this simple shell script to add a user
#!/bin/sh
echo Enter user login
read loginID
echo Enter user name
read username
gid_def=group
share_root=/u/shared
grep $loginID /etc/passwd
if [ $? -ne 1 ]
then
echo 'already in system '
else
echo "Adding user..."
useradd -G$gid_def -c"$username" -d /usr/$loginID $loginID
echo "Making user directory..."
mkdir /usr/$loginID
chown $loginID:$gid_def $loginID
echo "Set unix users password..."
passwd $loginID
echo "Set Facetwin password..."
fct_encrypt -b
fct_encrypt $loginID
mkdir /u/share/$loginID
chmod 700 $share_root/$loginID
fi
If you have any suggestions for improvement let me know.
Editor's note:
If you just want to quickly add a Linux user with default home
directory, etc, just do: (for example, to add "fred")
useradd fred
passwd fred
That will add the user, create the user's home directory
automatically with proper permissions, and complain if they already
exist.
Dirk has FacetWin and other
reasons for a more complex script. SCO's useradd doesn't
default.
If transferring SCO to Linux, see How can I transfer SCO accounts (passwd information) to Linux?.
More Articles by Dirk Hart
/DirkHart/dhuseradd.html copyright September 2003 Dirk Hart All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
I sell and support
Kerio Mail server
Click here to add your comments
---November 9, 2004
grep $loginID /etc/passwd
will not always work. You may have people
with almost same login names.
grep john /etc/passwd
will match *john*, *johnpaul*, *johnny*, etc.
---November 9, 2004
grep $loginID /etc/passwd
will not always work. You may have people
with almost same login names.
grep john /etc/passwd
will match *john*, *johnpaul*, *johnny*, etc.
---November 9, 2004
But that might be his intention - to avoid similar, possibly confusing id's.
If he did want to be specific, he can
grep $loginID: /etc/passwsd
--TonyLawrence
---November 9, 2004
grep $loginID /etc/passwd
will not always work. You may have people
with almost same login names.
grep john /etc/passwd
will match *john*, *johnpaul*, *johnny*, etc.
---November 9, 2004
But that might be his intention - to avoid similar, possibly confusing id's.
If he did want to be specific, he can
grep ^$loginID: /etc/passwsd
--TonyLawrence
---November 9, 2004
---November 9, 2004
grep $loginID /etc/passwd
will not always work. You may have people
with almost same login names.
grep john /etc/passwd
will match *john*, *johnpaul*, *johnny*, etc.
---November 9, 2004
you should instead do:
cut -d":" -f1 /etc/passwd | egrep ^$loginID$
---November 9, 2004
grep $loginID /etc/passwd
will not always work. You may have people
with almost same login names.
grep john /etc/passwd
will match *john*, *johnpaul*, *johnny*, etc.
---November 9, 2004
you should instead do:
cut -d":" -f1 /etc/passwd | egrep ^$loginID$
---November 9, 2004
But that might be his intention - to avoid similar, possibly confusing id's.
If he did want to be specific, he can
grep ^$loginID: /etc/passwd
Why use cut for this simple case?
--TonyLawrence
---November 9, 2004
grep $loginID /etc/passwd
will not always work. You may have people
with almost same login names.
grep john /etc/passwd
will match *john*, *johnpaul*, *johnny*, etc.
---November 9, 2004
you should instead do:
cut -d":" -f1 /etc/passwd | egrep ^$loginID$
---November 9, 2004
But that might be his intention - to avoid similar, possibly confusing id's.
If he did want to be specific, he can
grep ^$loginID: /etc/passwd
Why use cut for this simple case? And you don't need egrep for that either.
--TonyLawrence
---November 9, 2004
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar