From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TCC parse error.
Date: Tue, 09 Dec 2003 19:06:28 +0000 [thread overview]
Message-ID: <marc-lartc-107099688305246@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107099609504144@msgid-missing>
Arturaz,
To me, the error is clearly reported and identified, but perhaps you
overlooked it.
: <stdin>:59: invalid type conversion \
: (expected size in bytes instead of rate) near ")"
^^^^^^^^^^^^^^^^^^^^^
: line 59:
: $monika = class ( rate 8kbps, ceil 240kbps, burst 6kBps )
: { sfq ( perturb 10sec ); };
Try this instead:
$monika = class ( rate 8kbps, ceil 240kbps, burst 6kB )
{ sfq ( perturb 10sec ); };
burst is a bucket size in bits (b) or bytes (B).
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-12-09 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 18:38 [LARTC] TCC parse error Artūras Šlajus
2003-12-09 19:01 ` Artūras Šlajus
2003-12-09 19:06 ` Martin A. Brown [this message]
2003-12-09 19:34 ` Martin A. Brown
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-107099688305246@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.