--On Tuesday, October 11, 2005 17:24:27 +0200 Sebastiaan Veldhuisen <[EMAIL PROTECTED]> wrote:

Hi David,

I just committed a new version of Mon to CVS with *UNTESTED* support for
a  global exlude_period.  Download the latest from the sourceforge CVS
repository and put 'exclude_period = wd {Mon} md {8-14} hr {17-23}' into
your config file, next to the other global settings.  (You'll also  need
the current version of Mon::Client, since there were some protocol
changes between your version (0.99.2) and the 1.1 series.

That's great news! Thanks for the enhancement :) I'll test it in the
next days, but unfortunately i'm not allowed to use my own compiled code
in production machines. I'll have to wait until Suse updates its rpms.



Sorry to hear your employer ties your hands like that. 0.99.2 has some serious problems, including some that can trigger a perl bug that results in a perl segfault.


You're trying to put the exclude_period definition inside a period.  Put
it  above the first period definition and it should work.  (And in
current Mon  code this would generate a config file syntax error.)

I putted exclude_period above all other period definitions and now i get
a syntax error and mon won't start. What do you mean with "current"? Do
you mean CVS?  Right now I'm using version 0.99.2. Does it mean it is
not possible to use an exclude period with my mon version?


I don't remember whether the 1.0pre* series has this fix, but in 1.1* a unrecognized option in the period section will result in an error.

Can you post a snippet of your current config and the resulting error message?

-David

David Nolan                    <*>                    [EMAIL PROTECTED]
curses: May you be forced to grep the termcap of an unclean yacc while
     a herd of rogue emacs fsck your troff and vgrind your pathalias!

_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon

Reply via email to