From: Benny Pedersen <me@junc.org>
To: <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] tcptraceroute have buffer overflow in ipv6
Date: Thu, 14 Apr 2011 06:18:09 +0200 [thread overview]
Message-ID: <db128645fa1783501679511217f8f38c@localhost> (raw)
In-Reply-To: <201104141352.11354.paulcol@andor.dropbear.id.au>
> To capture both, redirect STDOUT first, then set STDERR to match:
> tcptraceroute ipv6.google.com 80 > /path/to/log/file 2>&1
i end with 2 empty files
would have being usefull if -d have turned stderr over to stdout for debug
what more can i try now ?
next prev parent reply other threads:[~2011-04-14 4:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 3:35 [gentoo-amd64] tcptraceroute have buffer overflow in ipv6 Benny Pedersen
2011-04-14 3:52 ` Paul Colquhoun
2011-04-14 4:18 ` Benny Pedersen [this message]
2011-04-14 5:19 ` Benny Pedersen
2011-04-14 5:33 ` Paul Colquhoun
2011-04-14 14:36 ` Frank Peters
2011-05-02 19:17 ` [gentoo-amd64] unsubscribe Guy Harrison
2011-05-02 20:19 ` Dale
2011-05-02 23:03 ` Guy Harrison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db128645fa1783501679511217f8f38c@localhost \
--to=me@junc.org \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox