Kinkie wrote:
On Mon, Mar 30, 2009 at 1:31 AM, Nagios
wrote:
* Nagios *
Notification Type: PROBLEM
Service: HTTP
Host: wiki.squid-cache.org
Address: wiki.squid-cache.org
State: CRITICAL
Date/Time: Sun Mar 29 16:31:55 PDT 2009
Additional Info:
Connection refused
Sorry guys.
Root
Hi Guys,
I gave this some thought. Why don't we build a system close to sendmail's
milter system. An API where by clients can plug in and offer services - one
can be a traffic counter, traffic limiter (as what we proposing here) and
maybe a URL block, a virus scanner etc.
I know that there a
On Mon, Mar 30, 2009 at 10:42 AM, Amos Jeffries wrote:
> Kinkie wrote:
>>
>> On Mon, Mar 30, 2009 at 1:31 AM, Nagios
>> wrote:
>>>
>>> * Nagios *
>>>
>>> Notification Type: PROBLEM
>>>
>>> Service: HTTP
>>> Host: wiki.squid-cache.org
>>> Address: wiki.squid-cache.org
>>> State: CRITICAL
Tsantilas Christos wrote:
Hi Amos,
Some comments about "#if X" and "#ifdef X".
The gcc compiler when X is not defined, always assume that it is 0 when
appeared in an "#if". So it is safe to use the #if instead of #ifdef.
But maybe there is problem with other compilers (If I am not wrong
visua
On 03/30/2009 03:16 AM, Pieter De Wit wrote:
> I gave this some thought. Why don't we build a system close to
> sendmail's milter system. An API where by clients can plug in and offer
> services - one can be a traffic counter, traffic limiter (as what we
> proposing here) and maybe a URL block, a
On Mon, 30 Mar 2009 11:38:31 -0600, Alex Rousskov
wrote:
> On 03/30/2009 03:16 AM, Pieter De Wit wrote:
>
>> I gave this some thought. Why don't we build a system close to
>> sendmail's milter system. An API where by clients can plug in and offer
>> services - one can be a traffic counter, traff
On 03/30/2009 01:00 PM, Pieter De Wit wrote:
> On Mon, 30 Mar 2009 11:38:31 -0600, Alex Rousskov
> wrote:
>> On 03/30/2009 03:16 AM, Pieter De Wit wrote:
>>
>>> I gave this some thought. Why don't we build a system close to
>>> sendmail's milter system. An API where by clients can plug in and offe
Ok - so here is how I see this :
* We need to agree (maybe a strong word) on a traffic "limiting" standard.
(Think how the limits are implemented, rather than done - if the object
size is known, pass that to the "limiter", if not, everytime data is RX'ed
using something like a session id or so)
Pieter De Wit wrote:
Ok - so here is how I see this :
* We need to agree (maybe a strong word) on a traffic "limiting" standard.
(Think how the limits are implemented, rather than done - if the object
size is known, pass that to the "limiter", if not, everytime data is RX'ed
using something li
Hi,
I am attaching a new patch, which:
- Add the files fs/Module.cc,h similar to esi/Module.cc
- Build a new library libfs.a
- The fs/aufs/StoreFSaufs.cc, fs/diskd/StoreFSdiskd.cc and
fs/ufs/StoreFSufs.cc now contain just fake pointers
- The FS::Init() method used to build ufs, aufs and
10 matches
Mail list logo
