I have a webpage that is in HTML and PHP. In PHP I have tried using exec, system, shell_exec and passthru functions to call an Expect Script file (temp.exp). This Expect file spawns a telnet session that uses "expect/send" commands to retrieve information from an environmental unit (not a normal... (0 Replies)
I call a EXPECT script from my perl script with machine IP and a FIle. The script logins to the machine and exports the value. The values to be exported or stored in a file.
I have close to 10 machines and I have created 10 files and pass the corresponding files in command line, Now I could like... (4 Replies)
Hi there,
I need some help regarding the execution of shell script from expect as the method I am trying is giving me error. I wrote an shell program which takes two arguments to telnet to a device and saves the output in a file. Following is the script.... (0 Replies)
Hi All,
I have an Expect script which logs into Cisco switch, performs a show interface command. I want to read a file of ip addresses which will be passed to the expect script.
The script to read the file works, the expect script works on it's own but when i call the 'expect' script from the... (12 Replies)
Hi all,
This is the first time i am using expect.
I am trying to call a function with in the shell script. The function will shh to a new server and will pass the password using expect and send. I need help in calling the fuction i am getting follaowing errors...
here the script
... (8 Replies)
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)
Shell Scipt: temp.sh
su - <$username>
expect pass.exp
Expect script: pass.exp
#!/usr/bin/expect -f
# Login
#######################
expect "Password: " send "<$password>\r"
it comes up with Password: but doesnt take password passed throguh file. (2 Replies)
I have an expect script called remote that I want to call from inside my expect script called sudoers.push, here is the code that is causing me issues:
set REMOTE "/root/scripts/remote"
...
log_user 1
send_user "Executing remote script as $user...\n"
send_user "Command to execute is: $REMOTE... (1 Reply)
Hi Team,
I have to execute a task from my local machine, where i keep my .expect,.sh, .bash and .python scripts .Task are coded in the script and has to be executed at remote machine.
for that i used following task
.....
SCRIPT 1:
cat shell_check.sh
read value
if
then
expect... (3 Replies)
Hi I am trying the following in my bash script which logs into my machine and runs a command. Trying to solve this using expect.
The first expect statement is hit and it enters the address "10.10.0.10" but when the second expect statement is hit it exits
#!/bin/bash
expect -c '
spawn... (2 Replies)
Discussion started by: skorada
2 Replies
LEARN ABOUT CENTOS
callback
callback(8) mgetty+callback manual callback(8)NAME
callback - call a user back, presenting a login prompt
SYNOPSIS
callback [-x<debuglevel>] [-V] [-l<modemlines>] [-m<initstring>] [-s<speed>] [-d] [-S] [phone-number]
DESCRIPTION
Call the given phone number (if none is given on the command line, ask user for one), and if a CONNECT is established, hand over control to
mgetty(8) to present user with a login name prompt.
callback is used for various purposes:
* security: make sure your users are who they pretend to be by calling a well-known phone number.
* cost savings: make your company call you back.
callback can be called directly from the command line (but you must be "root" to do this, otherwise callback can't signal mgetty), or from
mgetty's "login.config". See the login.config file shipped with mgetty for an example.
OPTIONS -x <debug level>
Use the given level of verbosity for logging - 0 means no logging, 5 is really noisy.
-V Print version number and quit.
-d Do not go into the background. This is helpful for debugging.
-l <modem lines>
Use the given modem lines. Multiple lines can be separated by ":", as with sendfax(8). Example: callback -l tty1a:tty2a
-m <init sequence>
Set the modem initialization sequence (as usual: expect send expect ...). This can do nearly everything, as long as it leaves the
modem command responses on (that is, no ATQ1 here!) and switches the modem to data mode (AT+FCLASS=0) if it is used in data/fax
mode.
-s <speed>
This is the bit rate that should be used for the machine-modem connection. Usually you'll set this via the "speed <nnnn>" option in
"callback.config".
-S Use the line where callback is started from for dialing out. Callback can make use of multiple modem lines, and with this options,
you can force it to use just one modem, the one where a call comes in.
CONFIG FILE
callback will read all its configuration at run-time from a file, usually called /etc/mgetty+sendfax/callback.config. See the documentation
in the mgetty.info manual for details.
DIAGNOSTICS
In most cases, callback can't print any error messages to the console, because it must detach itself immediately from the terminal, in case
someone wants to be called back on the modem line he called in. So, nothing to print messages to...
Because of this, all callback errors are logged to a protocol file (the extent of the data written is controlled by the "-x" option), espe-
cially including the reason why a call was not made, or what exactly failed.
Just two messages are printed on stdout, and those are self-explaining, a call from a non-root user, and an invalid option.
INTERNALS
How does it work?
This is a bit tricky, because of the way init(8) handles the utmp(5) file. You can't just have any program ask the user for a login name,
and then start a "login shell", it won't work (this is for the same reason mgetty(8) has to be started from /etc/inittab).
So, mgetty has to do the "asking for login name". But I do not want to have all that dialout code in mgetty, bloating it even more.
The way it works is this: callback dials out on a modem device. It will only take a modem device that has a mgetty watching over it (!).
When the connection is established (CONNECT), callback will send a signal SIGUSR1 to mgetty, which, in turn, will send the same signal back
to signal "I got your signal". callback then exits, and mgetty takes over the existing connection, prompts the user for a login name, and
forks off /bin/login.
Conclusion: this will not work with mgetty versions before February 04, 1996 (no support for this signalling), and if it doesn't work for
you, please send me BOTH the mgetty and the callback log file, otherwise it's very hard to find the bugs.
BUGS
callback is "alpha" code, not very stable right now.
callback is fairly dumb concerning retries.
callback must be run as root.
Most of the documentation consists of "reading the source".
SEE ALSO mgetty(8), ct(1)AUTHOR
callback is Copyright (C) 1993-1996 by Gert Doering, <gert@greenie.muc.de>.
greenie 27 Oct 93 callback(8)
09-16-2010
