|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Why `expect -D 1' does not work?
Post 302208412 by dearvoid on Monday 23rd of June 2008 09:40:48 PM
06-23-2008
Why `expect -D 1' does not work?
On my Ubuntu 6.06 system, expect -D 1 does not work: 
Quote:
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.06
DISTRIB_CODENAME=dapper
DISTRIB_DESCRIPTION="Ubuntu 6.06.2 LTS"
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; /usr/bin/expect -v
expect version 5.42.1
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; cat foo.exp
#!/usr/bin/expect -f
exit 0
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; /usr/bin/expect -D 1 foo.exp
1: exit 0
dbg1.0> <--- It exits after this prompt
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; bye
[$$=3913 $?=0] ; cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=6.06
DISTRIB_CODENAME=dapper
DISTRIB_DESCRIPTION="Ubuntu 6.06.2 LTS"
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; /usr/bin/expect -v
expect version 5.42.1
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; cat foo.exp
#!/usr/bin/expect -f
exit 0
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; /usr/bin/expect -D 1 foo.exp
1: exit 0
dbg1.0> <--- It exits after this prompt
-(dearvoid@LinuxEden:Forum)-(~/tmp)-
[$$=3913 $?=0] ; bye
|
|
10 More Discussions You Might Find Interesting
1. Shell Programming and 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
2. Shell Programming and Scripting
Hi All,
Using Expect script when I run it manually it works. But when I put the entry in crontab, the job is still running after 15 hours. The script was created as root. I don't think it's a permission issue. Any idea?
This is what I have under root crontab...
00 18 * * 1-5... (4 Replies)
Discussion started by: samnyc
4 Replies
3. Shell Programming and Scripting
Hello hello, did a quick search and didn't turn up anything helpful. I've got a book I'm sure has the answers, but I don't think I'll have time to finish it before this all has to work, so here goes~ if this isn't a good place to post and someone could direct me to another forum I'd appreciate... (1 Reply)
Discussion started by: Vryali
1 Replies
4. Shell Programming and Scripting
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
I have looked high and low, tryed lots of diffrent things but cant get a simple counter to work right.
what i need is to increase a count ever time it finishes the test, pass or fail. example TEST PASS 1, NEXT TEST PASS 2,
I curently have
set foo o
while {$foo <=5} {
incr foo
puts... (1 Reply)
Discussion started by: melvin
1 Replies
6. Shell Programming and Scripting
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
7. Programming
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
8. IP Networking
hi all. and sorry for the random question, but this sparkled a raging flame-war at work and i want more points of view
situation
a router, with linux of some sort,
dhcp client requesting for ip in wan1 (as usual with wan ports)
dhcp server listening in lan1, and assigning ip (as usual... (9 Replies)
Discussion started by: broli
9 Replies
9. Programming
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
10. UNIX for Beginners Questions & Answers
Hi; problem may be obvious, simple but I have to say it is somehow not easy to locate the issue.
I am doing some word extracting from multiline text.
Interacting in CLI seems to work without issues. First step is to add multiline text to a variable.
expect1.1>
expect1.1> set... (2 Replies)
Discussion started by: aldowski
2 Replies
LEARN ABOUT REDHAT
lsb_release
FSG(1) FSG FSG(1) NAME
FSG - manual page for FSG lsb_release v1.4 SYNOPSIS
lsb_release [OPTION]... DESCRIPTION
FSG lsb_release v1.4 prints certain LSB (Linux Standard Base) and Distribution information. With no OPTION specified it is the same as -v. OPTIONS
-v, --version Display the version of the LSB specification against which the distribution is compliant. -i, --id Display the string id of the distributor. -d, --description Display the single line text description of the distribution. -r, --release Display the release number of the distribution. -c, --codename Display the codename according to the distribution release. -a, --all Display all of the above information. -s, --short Display all of the above information in short output format. -h, --help Display this message. FILES
If the installation is LSB compliant, the "/etc/lsb-release" file should contain the LSB_VERSION field. The value of the field should be the version number of the LSB specification against which the installation is compliant. If the installation is not compliant, the above field should not be present. Optional fields are DISTRIB_ID, DISTRIB_RELEASE, DISTRIB_CODENAME, DISTRIB_DESCRIPTION and can be used to overwrite information which is parsed from the next file. The "/etc/[distrib]-release" file contains a description line which is parsed to get information (especially on currently non-LSB compliant systems). The required line style is: "Distributor release x.x (Codename)" Where Distributor can be a couple of words, but then concatenated (i.e. Linux Foo BarLinux Linux -> FooBarLinux), x.x starts with a digit followed by any non-blank characters, Codename will also be concatenated (blanks cleanup only). And release is a keyword not to be used in DISTRIB_DESCRIPTION if you don't want to overwrite "/etc/[distrib]-release" data. Notice: To support the Debian distributions' lack of information (see "/etc/debian_version" file) some have been directly added into the lsb_release script. EXAMPLES
The /etc/lsb-release file contains: LSB_VERSION="1.0" DISTRIB_DESCRIPTION="I enjoy using my distrib" And the /etc/foobar-release file contains: My Linux Distrib release 1.0RC4 (TryIt) $ ./lsb_release --all LSB Version: 1.0 Distributor ID: MyDistrib Description: I enjoy using my distrib Release: 1.0RC4 Codename: TryIt $ ./lsb_release -a -s 1.0 MyDistrib "I enjoy using my distrib" 1.0RC4 TryIt Then simply without the "/etc/lsb-release" file, that means result on a non-LSB compliant distrib: $ ./lsb_release -a LSB Version: n/a Distributor ID: MyDistrib Description: My Linux Distrib release 1.0RC4 (TryIt) Release: 1.0RC4 Codename: TryIt AUTHOR
Written by Dominique MASSONIE. REPORTING BUGS
Report bugs to <mdomi@users.sourceforge.net>. Include a complete, self contained example that will allow the bug to be reproduced, and say which version of lsb_release you are using. COPYRIGHT
Copyright (C) 2000 Free Software Group, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. FSG lsb_release v1.4 February 2003 FSG(1)