"Tasuki Yamamoto" <tasuki.y2k RemoveThis @earthling.net> wrote in message
news:b5f8c660.0309170330.1f4f711a@posting.google.com...
> Thought this is quite important since there effectively is no other
> tool on Windows 2000 that is able to offer this type of bandwidth
> control.
>
> Package: NetLimiter
> Version: 1.21 beta
> Platform: Windows 2000 Advanced Server SP2
>
> Apache 2.0.47 is picked up/recognised by NetLimiter. However,
> NetLimiter is unable to track (i.e. monitor) any outbound traffic,
> such as that created by large HTTP downloads. Thus, no limiting is
> possible since it appears that Apache is effectively doing nothing in
> the NetLimiter window. Also its bandwidth usage is not in the overall
> traffic stats. There is a clear divergence between NetLimiter traffic
> stats and firewall traffic stats, probably attributable at least to
> Apache.
I've never run Apache under Windows (can't see the point in doing half a
job, run it under Linux) but I'm guessing it behaves a little like the
Burst! BitTorrent client.
If you look at the Apache process in the Netlimiter window you should see a
little "+" sign to the left of it, click it. You should now see bandwidth
usage for each individual Apache process, this is where you'll do your
bandwidth throttling but you'll have to do it for each individual process.
To be honest you're better off packet shaping at the firewall, most of the
professional ones will offer some degree of bandwidth management.<!-- ~MESSAGE_AFTER~ -->
FAQ
Profile
Private Messages
Log in
