below cmd (to get current hour - 1) works in localhost...whereas to get the same value in remote host..no result.. looks some pharsing error...can someone help?
This isn't causing me a problem, but it is puzzling (& slightly worrying) me.
If I use tar to copy to a tape & the tape is write protected, I only get the message 'tar: tape write err' if there are a few files to copy.
eg. # tar cvf /dev/rStp4 /usr/data
will produce the messages
... (4 Replies)
hi frnds,
I have written a script as follows.
ssh username@servername "find $1 -type f -name $2 -mtime +1 -exec rm '{}' \;"
when i excute tis script i get error
FIND: Parameter format not correct
parameter 2 is the file name .. .
Thx in advance (6 Replies)
Hi,
get -ek s.Communicator.java The difference between the current date and the creation date of
the newest delta in the SCCS file is greater than 1 year.
Make sure that the system date is set correctly.
This message is only a warning. (co11)
14.3
... (0 Replies)
After run errclear, it will clean the err log file. After that, if I still need display the log has been cleared by errclear, how can I do?
thanks (5 Replies)
When I run a script with truss it is exiting with error.
Without truss the script runs fine!
How to understand it?
I have used the truss to resolve a 'magic' disappearing, but it brings own questions.
The main problem is in a backgroun script, which on one server just disapeares,... (5 Replies)
Hi All,
I am trying to run the below cmd thro' a script.
awk 'NR>=48&&NR<=(58-1)' $IN_FILE_NAME | tee $OUT_FILE_NAME
but I am getting an err while running the script. It gives the below err msg :
awk: syntax error near line 1
awk: bailing out near line 1
(P.S Note: When run the... (6 Replies)
I've been looking at this code too long. Maybe a fresh set of eyes can spot the:
"syntax error near unexpected token `(' ./phmenu ` tput cup 18 4: echo "Accept? (y) es or (n)o: "
This is the line in the code:
tput cup 18 4; echo "Accept? (y)es or (n)o: "
Thanks In Advance... (3 Replies)
Hello gurus, this is part of my script:
ls -1 ${MyFile} >> ${dir_log}ListFile${Now}.tmp
FILENUM=`cat ${dir_log}ListFile${Now}.tmp| wc -l | awk '{print $1}'`>> /dev/null
if
then
writeError "ERRORE: no file in directory for type ${FileName}!" >> ${LogFileName}
Close 1
fi... (7 Replies)
Hi, When I login to system. root or any of the user, I get Perl error message. Please advise....
When I login as a user.... I get this err.msg.
Terminal type is vt100
You have new mail.
bash: /usr/local/bin/perl: cannot execute binary file
when I login as root.
Terminal type... (2 Replies)
Hi gurus,
My Solaris version is
Solaris 10 1/06 s10s_u1wos_19a SPARC
Im getting I/O error while trying to ls -l a directory in Solaris SPARC box
the truss output from server is attached below
truss -fall -vall -wall -rall ls -la
12278/1: acl("./dat", GETACLCNT, 0,... (3 Replies)
Discussion started by: Solaris_Begin
3 Replies
LEARN ABOUT DEBIAN
shell-quote
SHELL-QUOTE(1p) User Contributed Perl Documentation SHELL-QUOTE(1p)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.8.4 2005-05-03 SHELL-QUOTE(1p)