#!/bin/sh
if [ $# -eq 0 ] ; then
echo "Usage: enshar filename1 filename2 [...]" >&2
exit 1
fi
for file in "$@"
do
if [ -d $file ]
then
echo "enshar: $file is a directory" >2
exit 1
elif [ ! -f $file ]
then
echo "enshar: $file does not exist" >2
exit 1
elif [ ! -r $file ]
then
echo "enshar: $file is not readable" >2
exit 1
elif [ -h $file ]
then
echo "enshar: $file cannot enshar" >2
exit 1
fi
cksum $file| read ck summy1 dummy2 # ck is the checksum
echo "\!EnShAr!\ "
# no idea what this line is doing. $1 cannot be used here and << makes no sense to me
# try writing this out, not as script, but as what you want done here...
"test $file = nnnnnnnnnn || echo $0: bad cksum in $file << '\!EnShAr!\'"
cat $file
done
does somebody know about SPOT ?? any link about SPOT commands ?
i ve made a mistake during configuration, :mad:
then i ve started the system in Maintenance mode
the only shell was SPOT. :eek:
SPOT doesn t understand anything....
how do i work with SPOT ?
thanks in advance
Karine... :D (1 Reply)
Hey
May be a dumb question
Can I use a SPOT which is at 5.3 TL6 to boot an LPAR (with 5.3 TL8) in to maintenance mode? Will it work ?
Is it mandatory that SPOT should be of same or higher version in such case?
Bala (1 Reply)
Hello im new here and i shot stright with question.
Mainly i wanna ask , how do i search with regexp in one spot and show the whole thing, what im trying to ask is , for eg. i do ls -l, and i see all the info for the dirs and dats. now say i wanna get all the dats that in their name they start... (2 Replies)
HI. there
My 10 servers are running on 6.1-05-03 aix including NIM server
but my user want to update a TL (61-05-03 to 61-06-04)
if I Update a AIx version of TL .. is that change the SPOT of NIM server..
OR if I make a spot of AIX7.1 and Is that support AIX 6.1 AIX 5.3 Images
I... (1 Reply)
Dear Admins,
The SPOT defined in NIM is for aix 5.3 TL 7 . Some of the NIM clients are upgraded to TL 10 . Now the SPOT level is older than the mksysb level.
This will cause problem during restoration of any NIM clients.
Now i want to upgrade SPOT level to TL 10 and redefine the resources... (3 Replies)
Hi there can anyone help me to spot my mistake and please explain why it appears
My code :
#!/usr/bin/gawk -f
BEGIN { bytes =0}
{ temp=$(grep "datafeed\.php" | cut -d" " -f8)
bytes += temp}
END { printf "Number of bytes: %d\n", bytes }
when I am running ./q411 an411
an411:
... (6 Replies)
Hi everyone!
Ok so I'm trying for the first time to install AIX on a LPAR with NIM.
The NIM:
root@oaexpnimp01(/home/root) # oslevel -s
6100-08-02-1316
I'm trying to install AIX 6.1 TL1. I successfully created a new lpp source
root@oaexpnimp01(/home/root) # lsnim -l AIX61_TL1_2... (10 Replies)
Discussion started by: trivium012
10 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)