On Thu, 17 May 2001, Daniel Feiglin wrote:
> This worked:
>
> strace -e trace=file -o jun.txt ethereal
>
> The tee thing didn't work. man strace, option -o.
strace sends its trace to stderr, not to stdout. You need something like:
strace 2>&1
And there you can fit 'tee' , or 'egrep "fstat|fo
Ariel Biener wrote:
> On Wed, 16 May 2001, Daniel Feiglin wrote:
>
>
> Without too much thinking, strace -f ethereal , redirect the output with
> tee to a file as well, and then change the config. Look in the strace
> output file, and you'll see what files it accesses.
>
> --Ariel
>
>
>
>>
guy keren wrote:
> On Wed, 16 May 2001, Daniel Feiglin wrote:
>
>
>> I got it going OK, but it has a silly default of sampling ALL protocols. After
>> labouriously switching them all off, but for those I wanted, I found next time
>> around, that my "setup" was not saved anywhere.
>>
>> Does an
On Wed, 16 May 2001, Daniel Feiglin wrote:
> I got it going OK, but it has a silly default of sampling ALL protocols. After
> labouriously switching them all off, but for those I wanted, I found next time
> around, that my "setup" was not saved anywhere.
>
> Does anyone know where Ethereal puts i
On Wed, 16 May 2001, Daniel Feiglin wrote:
Without too much thinking, strace -f ethereal , redirect the output with
tee to a file as well, and then change the config. Look in the strace
output file, and you'll see what files it accesses.
--Ariel
> Hello!
>
> Last week there was a discussion
Hello!
Last week there was a discussion about network sniffing tools. One mentioned was
ethereal, which is a nice alternative to the venerable tcpdump.
I got it going OK, but it has a silly default of sampling ALL protocols. After
labouriously switching them all off, but for those I wanted, I