On Mon, 2010-05-17 at 16:29 +0300, Michael Goldish wrote:
To disable tcpdump, set 'run_tcpdump = no' in a config file.
If 'run_tcpdump' isn't set at all, it defaults to 'yes'.
(Currently TAP mode cannot be used without tcpdump.)
Ok, I agree with your reasoning, commited as:
To disable tcpdump, set 'run_tcpdump = no' in a config file.
If 'run_tcpdump' isn't set at all, it defaults to 'yes'.
(Currently TAP mode cannot be used without tcpdump.)
Signed-off-by: Michael Goldish mgold...@redhat.com
---
client/tests/kvm/kvm_preprocessing.py |2 +-
On Mon, 2010-05-17 at 16:29 +0300, Michael Goldish wrote:
To disable tcpdump, set 'run_tcpdump = no' in a config file.
If 'run_tcpdump' isn't set at all, it defaults to 'yes'.
(Currently TAP mode cannot be used without tcpdump.)
Maybe we can just tie tcpdump execution to tap mode - if
On 05/17/2010 04:35 PM, Lucas Meneghel Rodrigues wrote:
On Mon, 2010-05-17 at 16:29 +0300, Michael Goldish wrote:
To disable tcpdump, set 'run_tcpdump = no' in a config file.
If 'run_tcpdump' isn't set at all, it defaults to 'yes'.
(Currently TAP mode cannot be used without tcpdump.)
Maybe