Re: tcpdump + IFS = no sense?
- From: tony.andreoli@xxxxxxxxx
- Date: 30 Aug 2006 07:28:09 -0700
Wierd, I've never experienced this, but putting "eval" in front solved
it.
Thanks.
David Schwartz wrote:
tony.andreoli@xxxxxxxxx wrote:
I'm setting it to a carriage return:
IFS="
"
As I've done a million times before. The result is the ability to read
a text file one line at a time rather than one word at a time. That
functionality still works fine, it's just that tcpdump is choking.
With IFS set to just a newline, bash interprets "tcpdump -i eth0" as
"tcpdump" "-i eth0" instead of "tcpdump" "-i" "eth0", which is what it
expects and requires.
DS
.
- References:
- tcpdump + IFS = no sense?
- From: tony . andreoli
- Re: tcpdump + IFS = no sense?
- From: Dale Dellutri
- Re: tcpdump + IFS = no sense?
- From: tony . andreoli
- Re: tcpdump + IFS = no sense?
- From: David Schwartz
- tcpdump + IFS = no sense?
- Prev by Date: Re: tcpdump + IFS = no sense?
- Next by Date: Re: IPTABLES MASQUERADE - WAN is OK but no LAN traffic...
- Previous by thread: Re: tcpdump + IFS = no sense?
- Next by thread: How Sticky Are CableModem AUPs?
- Index(es):
Relevant Pages
|