That's just not how if statements work in expect, if I'm reading it right. Most of your checks come down around like the below:
I don't have expect handy this second, but I think this would be right
You just need to adjust how you're doing if statements - bourne syntax isn't right for an expect/tcl script.
hi,
i wat to get the output of a grep command in a file. but when i am trying out the same grep command in the unix prompt its working fine.. i am getting the output properly.. but when i am writing the same command inside my shell script , its just creating a new output file with no contents... (1 Reply)
hi,
i wat to get the output of a grep command in a file. but when i am trying out the same grep command in the unix prompt its working fine.. i am getting the output properly.. but when i am writing the same command inside my shell script , its just creating a new output file with no contents... (11 Replies)
Hi all,
I am using the below given sqlplus command in my unix script to invoke a stored procedure which returns a value .It works fine.
RET_CODE=$(/opt/oracle/product/10.2.0.4.CL/bin/sqlplus -S $USER/$PASSWD@$DB_NAME <<EOF
EXEC MY_PKG.MY_SP (:COUNT);
PRINT COUNT;
commit;
... (6 Replies)
Hi All,
Is there any way to monitor a command inside shell script ? I have a script inside which I have a tar command which zips around 200GB data.
tar zcvf $Bckp_Dir/$Box-BaseBackup-$Day.tar.gz * --exclude 'dbserver_logs/*' --exclude postmaster.pid --exclude 'pg_xlog/*'
I want to... (3 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)
I am trying to execute expect command inside by small bash script to login into servers using key authentication method. My script is as follows:
#!/bin/bash
HOST=$1
/usr/bin/expect -c "
spawn ssh -i /root/.ssh/id_rsa root@$HOST
expect -exact "Enter... (3 Replies)
Hi I have two scripts one is Expect and other is shell.
I want to merge Expect code in to Shell script so that i can run it using only one script. Can somebody help me out ?
Order to execute: Run Expect_install.sh first and then when installation completes run runTests.sh shell script.
... (1 Reply)
Discussion started by: ashish_neekhra
1 Replies
LEARN ABOUT CENTOS
error::pass1
ERROR::PASS1(7stap)ERROR::PASS1(7stap)NAME
error::pass1 - systemtap pass-1 errors
DESCRIPTION
Errors that occur during pass 1 (parsing) usually mean a basic syntax error of some sort occurred in the systemtap script. There are sev-
eral classes of problems possible:
plain syntax error
The systemtap script parser detects a large variety of errors, such as missing operands, bad punctuation. It tries to list what
kinds of tokens it was expecting to see, and will show the region of the source code with the problem. Please review the stap(1)
man page and/or the tutorial, to correct the script's syntax.
grammar ambiguities
There is at least one known ambiguity in the systemtap grammar. It relates to the optionality of ; (semicolon) separators between
statements, and the ++ and -- increment/decrement operators. If the parser indicates an error, consider adding some explicit ; sep-
arators between nearby statements and try again.
missing command line arguments
A systemtap script that uses the $N and @N constructs for substituting in command-line options may fail if not enough options were
given on the stap command line.
compatibility changes
Some versions of systemtap have changed the language incompatibly, for example by adding the try/catch keywords for exception han-
dling. In such cases, rerun systemtap with the --compatibility=VERSION option, substituting the last systemtap version where your
script was known to work. You may also check the release-history NEWS file for compatibility changes.
GATHERING MORE INFORMATION
Increasing the verbosity of pass-1 with an option such as --vp 1 can help pinpoint the problem.
SEE ALSO stap(1),
error::reporting(7stap)ERROR::PASS1(7stap)