01-24-2009
Quote:
Originally Posted by
photon
I also found a great tool for snooping on network, besides brain 1.0.
so give us a link... maybe it helps other people also!
cheers,
DN2
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
How we can detect that there has been a data loss during FTP, throught Shell scripting?
I have gone through FTP return codes, but, none indicate that there has been any data loss.
Can we use FTP return code 226 as an indication that during file transfer there has been no data loss? If,... (4 Replies)
Discussion started by: sameerbo
4 Replies
2. UNIX for Advanced & Expert Users
I am experiencing a problem where under a dial condition I am experiencing packet loss, which is failrly normal, but the response to the packet loss is taking bewteen 6 and 10 seconds. Could someone please advise what the industry standard is on the response time under a packet loss senario. (1 Reply)
Discussion started by: shane
1 Replies
3. Ubuntu
Hello everyone,
I was trying to install db2 on Ubuntu, but got messed up with manual installation and Synaptic. At the moment, I find myself with a filesystem where DB2 is NOT installed ( I removed it with a sudo rm :o ) and with Synaptic still flagging db2exc as installed. The problem is that... (1 Reply)
Discussion started by: clalfa
1 Replies
4. IP Networking
I trying to send and receive OSPF packets. I am using RAW Sockets(socket(AF_INET, SOCK_RAW, IPPROTO_OSPF)) to do this.
I am successfully able to send an OSPF Hello packet however I am not able to receive a OSPF packet if I have not sent an OSPF packet earlier on the RAW SOCKET.
Scenario:
... (3 Replies)
Discussion started by: cosmic_egg
3 Replies
5. UNIX for Dummies Questions & Answers
Hi Gurus of UNIX, I has a problem when I try to install a packet in my virtual box. (I install solaris in it)
Any want can help whith it: The problem is the following
# pkgadd -d wireshark-1.2.10-sol10-x86-local
The following packages are available:
1 SMCwires wireshark
... (5 Replies)
Discussion started by: andresguillen
5 Replies
6. Solaris
Hi,
I am using the ce interface on my Solaris 9 server and there is significant packet loss when transmitting large packets. Does anyone have a fix for this?
----10.1.0.0 PING Statistics----
51 packets transmitted, 42 packets received, 17% packet loss
round-trip (ms) min/avg/max =... (12 Replies)
Discussion started by: sparcman
12 Replies
7. AIX
(5 Replies)
Discussion started by: Vishal_dba
5 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)