From: "hare ram" <hareram@sol.net.in>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Traffic shaping with transparent proxy
Date: Mon, 14 Apr 2003 14:46:34 +0000 [thread overview]
Message-ID: <marc-lartc-105033071105424@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105032900203487@msgid-missing>
Hi
If that is the case, iam also working on same
some recomendation given in this list is
htb and imq, iam still working, hope it make help you this hint to work
hare
----- Original Message -----
From: "Sebastian 'spax' Pape" <pape@rbg.informatik.tu-darmstadt.de>
To: "hare ram" <hareram@sol.net.in>
Cc: <lartc@mailman.ds9a.nl>
Sent: Monday, April 14, 2003 7:51 PM
Subject: Re: [LARTC] Traffic shaping with transparent proxy
> hi!
>
> > If you are using Transparent cache ( Squid)
> > better you use delay pools, it works greate like large downloads to be
> > controled
>
> I'm not really up to date with delay pools, but as far as I remember they
> only shape the traffic of squid among all squid-users and don't know
> anything about the available bandwidth. So the problem to allocate
> bandwidth to squid (vs. other traffic like, ssh, ftp, smtp, ...) still
> remains or am I getting something wrong here?
>
> best regards
>
> Sebastian
>
> --
> Sebastian 'spax' Pape | Better to remain silent and be thought a
fool
> mailto: sebastian@p-a-p-e.de | than to speak and remove all doubt.
> gpg: http://p-a-p-e.de/gpg.asc |
> --- Do you want to know more? http://www.p-a-p-e.de/ ---
>
_______________________________________________
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-04-14 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 13:59 [LARTC] Traffic shaping with transparent proxy Sebastian 'spax' Pape
2003-04-14 14:21 ` Sebastian 'spax' Pape
2003-04-14 14:31 ` hare ram
2003-04-14 14:46 ` hare ram [this message]
2003-04-14 15:48 ` Stef Coene
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-105033071105424@msgid-missing \
--to=hareram@sol.net.in \
--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.