11-03-2011
Quote:
Originally Posted by
nanochan1
any assistance ? I've tried numerous attempts but still can't see why anything <10 works and > doesn't
You changed your data format again since you wrote that, so I didn't think that question still applied.
I'm with vgersh99 on this one -- the program has flaws, not just errors. Fixing it means rewriting it.
7 More Discussions You Might Find Interesting
1. Programming
please refer the following 2 statements...
1)
int i=1,j;
j= i++ + i++;
2) int i=1,j;
j=++i + ++i;
how j becomes 2 and 6 for the above 2 statements
respectively ???
( i guessed j must be 3 and 5)
Somebody define the exact reason please.. :(
... (2 Replies)
Discussion started by: shamal
2 Replies
2. BSD
Hi Guys...(if anyone is out there), do these specialist posts ever get answered and do we just have to bide our time and be patient, or whats the deal (3 Replies)
Discussion started by: Gerry405
3 Replies
3. Shell Programming and Scripting
Hi everybody,
I have been looking for an answer to this issue both on google and on the forum, but I couldn't find anything. please help me :eek:
As part of an automated (in perl) install of Solaris 9, I would like to be able to answer automaticaly to the question the installer asks.... (2 Replies)
Discussion started by: zaap
2 Replies
4. UNIX for Dummies Questions & Answers
hey, have been set this question at school and cannot think for the life of me how to do this. Ive thought about setuid/setgid and things like that but cant make any snese of it. Can anyone help?
question reads:
You have a file which has the names, email addresses,
mobile numbers and sales... (1 Reply)
Discussion started by: biffa
1 Replies
5. Shell Programming and Scripting
hi,
i'm using the folowing ssh command to list the newuser "crontab' from myuser
ssh -t myuser@host1 "sudo -u newuser crontab -l"
this is ok but it is asking me a password.
Mot de passe de myuser:
The problem is that i want to answer it automatically in a shell script with the... (22 Replies)
Discussion started by: Nicol
22 Replies
6. Shell Programming and Scripting
I am new to perl and want to get a little better understanding of debugging code in perl. I have a perl script that has questions to be answered like:
he following PERL modules are recommended:
Crypt::DES
Crypt::PasswdMD5
IO::Pty
Net::Write::Layer2
String::CRC32
Attempt to install... (0 Replies)
Discussion started by: metallica1973
0 Replies
7. UNIX for Dummies Questions & Answers
Hello All,
mgetty Version: 1.1.36
OS: OpenSuSE 13.1 (armv7l)
Modem: Zoom 56K USB Modem Model 3095
So I've been playing with mgetty for weeks now testing dialing into the USB modem from another PC using the same modem and connecting
using minicom (*minicom ---dials to---> mgetty). I had... (3 Replies)
Discussion started by: mrm5102
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)