Try creating an extra script that contains:
and run that. Does that have the same problem?
If so, see if putting a sleep 10 between start-openstack.sh and the glance statement makes a difference.
If it does, then you can lower 10 seconds to a lower number..
Yes, problem has been solved by adding
after;
Thanks
Hi, i would like a help with this problem.
i have the following situation:
4 workstations SUNs:
SunOS porsche 5.8 Generic_117350-18 sun4u sparc SUNW,Sun-Blade-100
SunOS jaguar 5.8 Generic_108528-18 sun4u sparc SUNW,Sun-Blade-100
SunOS mercedes 5.8 Generic_117350-18 sun4u sparc... (2 Replies)
Hi friends,
i have written one small script named as "size.sh".....
while running its giving
syntax error at line no 2: 'str=$' unexpected.
How to run this file ??? please help me.
file content is :
-----------------------------
#!/bin/sh
str=$( df -k | grep /usr/local)... (14 Replies)
hey,
i'm trying to run several processes due 2 loops :
the code is:
cd ${TIBCO_HOME}/tra/domain/${DOMAIN}/application/
for app_name in ls *
do
echo $app_name
if && && ;
then
exit
else
echo $app_name
cd $app_name
pwd
for ps_name in ls *.sh
do
echo... (2 Replies)
Hi All,
I am running a script which is present on remote machine using ssh command.
the remote script is failing when try to load a property file. It says file does not exist.
Any idea what should be the problem for this.
Thanks
Supriya. (7 Replies)
While executing perl scriptit gives some compling issue, please help out
$inputFilename="c:\allways.pl";
open (FILEH,$inputFilename) or die "Could not open log file";
Error : Could not open log file at c:\allways.pl line 4
learner in Perl (1 Reply)
Hi,
I have following K script, that is in rc0.d directory to be run on shutdown. It's linked using the 'ln' command to init.d.Can anyone tell me as to why it's not running, or if i have incorrect syntax?I get:
"test: argument expected
type=uname -p
+ "
When running it with sh -x
... (8 Replies)
I am trying to use the CRON utility in Fedora 11 & CentOS...
I intend to run a script which pops up a warning message every hour and i made the following entry using "CRONTAB -e "
* * * * * sh /bin/myscript.sh
But this does not seem to be running.
Another thing to note is that,... (4 Replies)
Hi all,
I have a script that calls another program/script, xxx, to run in the background. Supposedly this program at most should finish within five (5) minutes so after five (5) minutes, I run some other steps to run the script into completion.
My problem is sometimes the program takes... (5 Replies)
I have getting problem with running gs on a non global zone. This is new zone. Seems something to do with library, but I am not getting correct pointer.
-bash-3.00$ which gs
/usr/local/bin/gs
-bash-3.00$ gs
ld.so.1: gs: fatal: libcairo.so.2: open failed: No such file or directory
Killed... (3 Replies)
Discussion started by: solaris_1977
3 Replies
LEARN ABOUT CENTOS
shell-quote
SHELL-QUOTE(1) User Contributed Perl Documentation SHELL-QUOTE(1)NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS --debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.16.3 2010-06-11 SHELL-QUOTE(1)