Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Using Expect for the first time
Top Forums Shell Programming and Scripting Using Expect for the first time Post 303025424 by gull04 on Friday 2nd of November 2018 08:13:38 AM
Old 11-02-2018
Hi,

I do this using two quickly hacked together scripts as follows - please bear in mind that these scripts are running on Solaris 11 and things are done this way to avoid a problem. But the scripts should be easily adaptable.

Script 1

Code:
for USER in `cat $DATADIR/name_list.txt | awk -F: '{ print $1 }'`
        do
if [ ! -d /export/home/${USER} ]
        then
                echo "The home directory for ${USER} does not exist - create."
                mkdir -p /export/home/${USER}
                if [[ $? -eq "0" ]]
                then
                        useradd -c"XXX Support User" -d/export/home/${USER} ${USER}
                        if [[ $? -eq "0" ]]
                        then
                                echo "Account for user ${USER} Created."
                        else
                                echo "Accounr for user ${USER} could not be created."
                        fi
                else
                        echo "The Account for ${USER} either already exists or could not be setup."
                fi

                echo "Setting the ownership for /export/home/${USER}"
                chown ${USER}:staff /export/home/${USER}
                if [[ $? -eq "0" ]]
                then
                        echo "The ownership of /export/home/${USER} wasx successfully set."
                else
                        echo "There was a problem setting the ownership on /export/home/${USER}"
                fi
                echo "Setting the password for ${USER}"
                echo ${USER} >> $DATADIR/added_users.txt
                ${BINDIR}/set_pw.sh ${USER} Ch4ng3me
        else
                echo "The user ${USER} already exists."
fi
done

Script 2

Code:
#!/usr/bin/expect

set username [lindex $argv 0];
set newpass [lindex $argv 1];


# opem shell
spawn $env(SHELL)
# send passwd command
send "passwd $username\n"
expect "New Password:"
send "$newpass\n"
expect "Re-enter new Password:"
send "$newpass\n"
expect eof"
expect "# "
send "exit\n"

I would suggest that you modify the expect script to suit your environment and call it from your main script passing the variables as I do - it's easier that way I think.

Regards

Gull04
This User Gave Thanks to gull04 For This Post:
dakelly
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Long time since I used "expect"

Hello all, It's been a few years since I touched 'expect' and just got it on my system. In the past, I could simply do the following: (this is just a simple example) $ expect $ ls -l $ pwd $ exit ...then a default script name would be placed in my working directory. At this point I... (2 Replies)
Discussion started by: scriptosaurus
2 Replies

2. Shell Programming and Scripting

Expect and auto expect command

I need to run a remote application(GUI) in a client.i.e on running a script in the client machine i should get the GUI application which is running in the server by providing password through the script.Will expect or autoexpect command suit for this scenario? could anyone help me by posting some... (0 Replies)
Discussion started by: arun_v
0 Replies

3. Shell Programming and Scripting

strange expect script behavior, or am i misunderstanding expect scripting?

Hello to all...this is my first post (so please go easy). :) I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies

4. Shell Programming and Scripting

Need help with Expect script for Cisco IPS Sensors, Expect sleep and quoting

This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies

5. Shell Programming and Scripting

Expect - Comparison of expect value and loop selection

Hello All, I am trying to automate an installation process using expect and sh script. My problem is that during the installation process the expected value can change according to the situation. For Example if this is a first time installation then at step 3 I'll get "Do you want to accept... (0 Replies)
Discussion started by: alokrm
0 Replies

6. Programming

Calling expect script inside another expect

Hi, Am very new to expect scripting.. Can You please suggest me how to call an expect script inside another expect script.. I tried with spawn /usr/bin/ksh send "expect main.exp\r" expect $root_prompt and spawn /usr/bin/ksh send "main.exp\r" expect $root_prompt Both... (1 Reply)
Discussion started by: Priya Amaresh
1 Replies

7. Shell Programming and Scripting

Expect script to suspend expecting for a time period.

I have a simple Expect script to power a system on and off in an endless loop looking for an ERROR message at which point the script should exit. But I need to skip the first 60 seconds after each power on or off and not exit if there are ERROR messages during that time. I thought I could use... (0 Replies)
Discussion started by: David_Gilhooly
0 Replies

8. Shell Programming and Scripting

Expect script idles for a long time

the following code works sometimes. other times, it behaves mysteriously. when the script sshs to a box, it is suppose to automatically begin running the command it is told to run. but in this case, after this script logs into a host, it just sits there at the prompt and does not run the... (1 Reply)
Discussion started by: SkySmart
1 Replies

9. Programming

Expect script returning string following a found expect.

I'm fairly new to scripting so this might not be possible. I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version: #show version ... (0 Replies)
Discussion started by: IBGaryA
0 Replies

LEARN ABOUT OSX

su

SU(1)							    BSD General Commands Manual 						     SU(1)

NAME

     su -- substitute user identity

SYNOPSIS

     su [-] [-flm] [login [args]]

DESCRIPTION

     The su utility requests appropriate user credentials via PAM and switches to that user ID (the default user is the superuser).  A shell is
     then executed.

     PAM is used to set the policy su(1) will use.  In particular, by default only users in the ``admin'' or ``wheel'' groups can switch to UID 0
     (``root'').  This group requirement may be changed by modifying the ``pam_group'' section of /etc/pam.d/su.  See pam_group(8) for details on
     how to modify this setting.

     By default, the environment is unmodified with the exception of USER, HOME, and SHELL.  HOME and SHELL are set to the target login's default
     values.  USER is set to the target login, unless the target login has a user ID of 0, in which case it is unmodified.  The invoked shell is
     the one belonging to the target login.  This is the traditional behavior of su.

     The options are as follows:

     -f      If the invoked shell is csh(1), this option prevents it from reading the ``.cshrc'' file.

     -l      Simulate a full login.  The environment is discarded except for HOME, SHELL, PATH, TERM, and USER.  HOME and SHELL are modified as
	     above.  USER is set to the target login.  PATH is set to ``/bin:/usr/bin''.  TERM is imported from your current environment.  The
	     invoked shell is the target login's, and su will change directory to the target login's home directory.

     -	     (no letter) The same as -l.

     -m      Leave the environment unmodified.	The invoked shell is your login shell, and no directory changes are made.  As a security precau-
	     tion, if the target user's shell is a non-standard shell (as defined by getusershell(3)) and the caller's real uid is non-zero, su
	     will fail.

     The -l (or -) and -m options are mutually exclusive; the last one specified overrides any previous ones.

     If the optional args are provided on the command line, they are passed to the login shell of the target login.  Note that all command line
     arguments before the target login name are processed by su itself, everything after the target login name gets passed to the login shell.

     By default (unless the prompt is reset by a startup file) the super-user prompt is set to ``#'' to remind one of its awesome power.

ENVIRONMENT

     Environment variables used by su:

     HOME  Default home directory of real user ID unless modified as specified above.

     PATH  Default search path of real user ID unless modified as specified above.

     TERM  Provides terminal type which may be retained for the substituted user ID.

     USER  The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root).

FILES

     /etc/pam.d/su  PAM configuration for su.

EXAMPLES

     su man -c catman
	    Runs the command catman as user man.  You will be asked for man's password unless your real UID is 0.
     su man -c 'catman /usr/share/man /usr/local/man'
	    Same as above, but the target command consists of more than a single word and hence is quoted for use with the -c option being passed
	    to the shell.  (Most shells expect the argument to -c to be a single word).
     su -l foo
	    Simulate a login for user foo.
     su - foo
	    Same as above.
     su -   Simulate a login for root.

SEE ALSO

     csh(1), sh(1), group(5), passwd(5), environ(7), pam_group(8)

HISTORY

     A su command appeared in Version 1 AT&T UNIX.

BSD
								September 13, 2006							       BSD
All times are GMT -4. The time now is 07:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy