Re: alternatives to ETRN

[Andy Poling <andy@realbig.com>]

On Fri, 1 Aug 1997, Matti Aarnio wrote:
[...]
> > I even thought about mail processing. NROUTERS is defined in
> > /etc/zmailer.conf and contains number of routers running. I thought this
> > number could be sometimes too big and someties too low on the same machine.
> > Wouldn't it be better to make it virtual ?
[...]
> 	Perhaps.  I do have thought of it, but not done anything for it.
> 	Like with scheduler, the router needs to collect new jobs, and
> 	then process them.

I think this statement is key.


> 	Things will become more complicated, when the queue processing
> 	wants to do also router resource management, for example by
> 	starting up additional working routers, if the queue is long,
> 	and to cut down the number of routers, when there is no more
> 	work, and they have been idle for some preset time.
> 
> 	Would somebody want to do such code ?

Maybe I'm over-simplifying, but it sounds like you could largely re-use the
code that scheduler uses to do almost exactly the same sort of thing?  It
does such process management, and then its behavior could be fully
configurable...

-Andy

Global Auctions