--On May 2, 2007 9:33:23 PM +0200 Ruzsinszky Attila <suppressed> wrote: >> but if the config file is very large, one uxmon process may not be able >> to accomplish all the tests within the cycle time. In other words, if >> you have too many things for it to do in the file, it won't be able to >> do them often > > So how many "things" can be in the uxmon-asroot file? depends on how fast your uxmon workers get their work done. that's the problem. if thigs are slow (you have real problems and tests start timing out or whatever) then the uxmon worker falls behind and unrelated tests go purple. there's no clear cut answer... > Net check was solved with this config additon: [snip] > The additions are: interface=~bridge interface=~softwareLoopback [snip] > I thought the last two interfaces will be removed! ok, I see what you're doing there. I'm not familiar with ~'ing out interfaces with that test... but your orig Q, which I was answering, was about uxmon 'getting weird'... how is your uxmon acting weird? my first thought is that tuning your network test (to remove interfaces) has nothing to do with how many tests you have in the uxmon file. adding/removing a couple tests, or ~'ing out a few interfaces in one network test shouldn't make uxmon act weird... -c ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bigsister-general mailing list suppressed https://lists.sourceforge.net/lists/listinfo/bigsister-general
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.