05-26-2009
Quote:
Why?
$@ was there to replicate for ls the arguments given to the command hls, so that you can say for example:
hls -rS /bin/*
this is what am saying is not needed at all, when the command is piped through the output of the command will be automatically piped through
7 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
Fun With Automounting on FreeBSD
Link: Nice tips for FreeBSD Unix.
http://ezine.daemonnews.org/200202/automounting.html (2 Replies)
Discussion started by: killerserv
2 Replies
2. UNIX for Dummies Questions & Answers
ok, i've figured out my problem with distributed, in Solaris GUI if you click on a tar file it will untar it for you, using paramiters I don't know.
now, I've got a tar file in / called
dnetc-solaris26-x86.tar
i want to install it to the "/Veitch" directory
how exactly do I use the tar... (17 Replies)
Discussion started by: veitcha
17 Replies
3. UNIX for Advanced & Expert Users
Hai Friends
I have installed FreeBSD in my system... I have installed it to work in text mode don't have the GUI. The default text color is Black background with White Foreground. I want it to be with Black background with Green Foreground. How could i do that.
Thanks in advance
Collins (4 Replies)
Discussion started by: collins
4 Replies
4. Shell Programming and Scripting
uggc://ra.jvxvcrqvn.bet/jvxv/EBG13
#!/usr/bin/awk -f
BEGIN {
for (n=0;n<26;n++) {
x=sprintf("%c",n+65); y=sprintf("%c",(n+13)%26+65)
r=y; r=tolower(y)
}
}
{
b = ""
for (n=1; x=substr($0,n,1); n++) b = b ((y=r)?y:x)
print b
}
... (0 Replies)
Discussion started by: colemar
0 Replies
5. UNIX for Dummies Questions & Answers
I have a file called mytitles.txt containing a list of book titles
I have a second file called abfile.txt containing a list of book titles (in the 3rd field) and it has author info and copyright year info as well..
I want to search mytitles.txt for a match in the 3rd field of abfiles.txt, and... (2 Replies)
Discussion started by: glev2005
2 Replies
6. War Stories
Hi Folks,
I came accross this picture taken a number of years ago now, I just thought I'd share it with you guys. We were in the process of removing equipment from the Data Centre and had followed the cable through to this area, where one of the old patch areas had been.
When we lifted the... (2 Replies)
Discussion started by: gull04
2 Replies
7. Shell Programming and Scripting
Hey guys,
This is purely just a little bit of fun with awk. I realize this this isn't that constructive so please remove if need be.
Your goal:
Create a one line awk script that generates a diamond shape of any
size. Both the size of the diamond (measured by its middle line) and
the... (7 Replies)
Discussion started by: pilnet101
7 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)