Rainer Jung wrote:
E.g. if one empties the uriworkermap.properties, reloading it does not
change the internal mount list. Temporarily adding and later removing an
entry will not remove the entry.
That's the entire point.
But this is not what a user expects from a change in a list.
I know, bu
Rainer Jung wrote:
If you think you can do that in a simple way, then fine.
But if it would require a lots of changes, then I think
we should go with the more powerful solution as part
of 1.3 branch, by using shared memory, web interface, etc.
I just don't think that this is so important if yo
On Tue, 2006-11-21 at 11:58 +0100, Rainer Jung wrote:
> Henri Gomez schrieb:
> > Why not just extends current jkstatus ?
>
> Mapping rules are kept process local. They are only shared, because the
> first process generates them and afterwards all other processes inherit
> them during fork.
>
> To
JkMount shouldn't be affected by any automatic reloading to preserve
compatibility.
The new mounts via uriworkermap.properties chould be considered
transient, ie they could follow the file change but did the 60s isn't
too long is some circumstance ?
I think it will be better to make the Routing
Henri Gomez schrieb:
> Why not just extends current jkstatus ?
Mapping rules are kept process local. They are only shared, because the
first process generates them and afterwards all other processes inherit
them during fork.
To make the rules manageable via jkstatus (everyone wants that, me too;
Jean-frederic Clere schrieb:
> On Tue, 2006-11-21 at 06:52 +0100, Mladen Turk wrote:
>> Rainer Jung wrote:
>>> E.g. if one empties the uriworkermap.properties, reloading it does not
>>> change the internal mount list. Temporarily adding and later removing an
>>> entry will not remove the entry.
>>
On Tue, 2006-11-21 at 06:52 +0100, Mladen Turk wrote:
> Rainer Jung wrote:
> >
> > E.g. if one empties the uriworkermap.properties, reloading it does not
> > change the internal mount list. Temporarily adding and later removing an
> > entry will not remove the entry.
>
> That's the entire point.
