On Tue, Nov 23, 1999 at 04:49:38PM -0600, Marc Mongeon wrote:
> Jean-Yves:
>
> Hello, again. I'm doing fine. And you?
Fine, thanks Marc.
> I see now what you're talking about. I've never heard of these kinds
> of upload limits before, either because they aren't common in the U.S.,
> or because I've always had a dial-up connection that charges based
> on time.
That a mess: my provider ad about speed and unlimited connection, but
he put an upload limit, AND it is not able to supply a good service
(its not unusual to download @... less than 1 KB/s during the day)
> Now that I understand your question, I can tell you that you might be
> able to use IP accounting to do what you want. Using ipfwadm, set
> up an accounting rule to count all outgoing packets. Then, run a
> cron job every few minutes to check the packet count (I think you
> can find this info in /proc/net/ip_acct), and shut down the server
> if the byte count gets close to 500MB ("/etc/init.d/apache stop"
> to shut down the server).
Super, that's exactly the way I what it to work!
> As far as the choice of a web server, I can tell you that I have set
> up a 486 with 16M of ram for use as a web server, and it works
> just fine. I'm not sure what other options are out there.
Great, I have no choice, I only own 16MB of EDO.
> Concerning security, anytime you have a permanent connection to
> the Internet, security becomes more of an issue. I don't think that
> running a web server all the time really affects that one way or
> another.
Ok that's what I tought, but now I've got the confirmation :)
Thanks for that, I'll keep you aware of the progress.
But for now, I have to learn HTML, and it might take time...
JY
--
Jean-Yves F. Barbier <[EMAIL PROTECTED]>
Real computer scientists don't comment their code. The identifiers are
so long they can't afford the disk space.
