Martin Pala <address@hidden> writes:
Jan-Henrik Haukeland wrote:
But right now, I think we could doucment us out of the problem and
maybe refactor the code in a later 4.1 version. What do you think?
Yes, it is possible, no problem. This could involve lot of changes and
it is not critical for 4.0 => we don't need to implement it
now. Though i preffer to solve it in 4.0 - it is more logical then
present behavior + it can involve (small) language change and it could
be better to do it at once.
Hmm, yes, the only change exposed in the control file is (probably) a
new action. For instance; action unmonitor (a better name than
unmonitor preferably). This means that it will not crash with the
backward compability to the current 4.0 control file. Since it only
adds to a statement and does not change it.
I can implement it as soon as i'll be back. Please choose what you
like better :)
Well, since you will be gone for a week, it probably means that you
can have it ready first at the end of August.
Lets say that if we are not ready with a new release before the end of
August it could be interesting to include it (if it's ready) if not I
do not feel that this is a showstopper for the 4.0 release. And if
Rory is ready with the porting next week and I have fixed the SIGSEGV
problem, it is very tempting (at least in my book) to do a 4.0 release
sometime between 25-29 August. It is 1/2 year since monit 3.2 was
released.
Anyway lets see how it turns out when you get back. (If I have time
maybe I can implement this myself the next week instead, lets see.)