Здравствуйте, Questions.
There will be very usefull to have options for tcpdump to monitor
incomint or outgoing traffic regardless of src/dst IPs or ports or protocol
For example:
kes# tcpdump -n -i rl4 out
EXPECTED: show traffic outgoing on rl4
ACTUAL: tcpdump: syntax error
kes# tcpdump -n
On Sun, Jan 04, 2009 at 04:05:00PM +0200, KES wrote:
There will be very usefull to have options for tcpdump to monitor
incomint or outgoing traffic regardless of src/dst IPs or ports or protocol
For example:
kes# tcpdump -n -i rl4 out
EXPECTED: show traffic outgoing on rl4
ACTUAL:
On Sun, Jan 4, 2009 at 10:56 AM, Eugene Grosbein eu...@kuzbass.ru wrote:
On Sun, Jan 04, 2009 at 04:05:00PM +0200, KES wrote:
There will be very usefull to have options for tcpdump to monitor
incomint or outgoing traffic regardless of src/dst IPs or ports or
protocol
For example:
Hi,
On Thu, Jan 01, 2009 at 11:42:12PM -0800, Doug Barton wrote:
In working on cross-platform support for mergemaster I came across the
following problem. I set MAKEOBJDIRPREFIX to be that of the temproot
environment, which works fine when you do not specify a TARGET_ARCH.
When you do specify
Christian Weisgerber wrote:
Bruce Cran br...@cran.org.uk wrote:
I'm running 8.0-CURRENT amd64 here on a Turion64 X2 machine. Without
malloc debugging (malloc.conf - aj) 'make test' takes 25s; after
removing malloc.conf thus turning on debugging, it takes over 10
minutes.
Wow! That. Is.
Ruslan Ermilov wrote:
mergemaster.sh uses obj and all targets which aren't cross-build
aware (don't take ${TARGET} into account) to build etc/ bits, and then
distribution target (which is cross-build aware) to install then.
The effect of this is that you end up with build and install targets
On Monday 05 January 2009 02:26:38 Eugene Grosbein wrote:
On Sun, Jan 04, 2009 at 04:05:00PM +0200, KES wrote:
There will be very usefull to have options for tcpdump to monitor
incomint or outgoing traffic regardless of src/dst IPs or ports or
protocol
For example:
kes# tcpdump -n
7 matches
Mail list logo
