[Raw Msg Headers][Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: scheduler channel/host grouping

> Matti Aarnio <mea@nic.funet.fi>
> > > Couldn't this be coded as several patterns with one ser of parameters?
> > 	Such would require somewhat radical changes at the files:
> > 	"scheduler/readconfig.c", and "scheduler/scheduler.c",
> > 	plus likely at the main datastructures relating to the
> > 	channel/host selectors, and groupings.
> Que?  I thought that worked already.  The scheduler man page says:
>        If the clause is empty (i.e., consists only of a pattern),
>        then  the  contents  of  the next non-empty clause will be
>        used.
> I've never had a use for this particular feature, but it -does- sound
> rather like what you want.

	I have to verify that -- next week, but I think if it works
	this way anymore at all, then it effectively generates SEPARATE
	resource pools (thread-groups) for each of the clauses.  That is,
	doing it will not define a single thread-group which handles 
	"smtp/*.foo" and  "smtp/*.faa", like my   "smtp/*.{foo,faa}"  does.

	Now I am to step on a car, and drive across Finland to a radio-
	amateur summer convention :-)

> --Arnt

	/Matti Aarnio <mea@nic.funet.fi>