From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] rt_acct usage
Date: Sat, 17 Mar 2001 11:35:15 +0000 [thread overview]
Message-ID: <marc-lartc-98482901325642@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98455289815187@msgid-missing>
On Fri, Mar 16, 2001 at 11:41:36AM +1030, Joel@airnet.com.au wrote:
> Okay, I found that. My rt_acct file doesn't have any entries, but the
> headers in the utility look like it'd be useful. Do you have to mark routes
> in a special way to get them to be accounted through this, or something like
> that?
I have no clue. If you ever figure it out, we'll dedicate a chapter in the
HOWTO to it.
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-03-17 11:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-14 6:54 [LARTC] rt_acct usage Joel
2001-03-15 11:32 ` bert hubert
2001-03-16 1:23 ` Joel
2001-03-17 11:35 ` bert hubert [this message]
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=marc-lartc-98482901325642@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@vger.kernel.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