From: Schwimmer, E. E *H. <EE...@hs...> - 2007-03-15 20:45:34
|
Hi again Etienne, Yeah, I put some very basic regex evaluation code in devmon, but it would be pretty difficult to write something that would find all problems with user-supplied regular expressions. Could you run devmon in the foreground (ideally with --debug) and let me know where it dies? I'll put some more parent-checking code in the child code to make them shutdown if they find their parent is MIA. -Eric > -----Original Message----- > From: dev...@li... [mailto:devmon-support- > bo...@li...] On Behalf Of Marganne, Etienne > Sent: Thursday, March 15, 2007 4:18 AM > To: dev...@li... > Subject: [Devmon] New templates and process errors >=20 > Hello, >=20 >=20 >=20 > I am actually developing new templates for Nokia VPN boxes, Checkpoint > firewalls and Netilla boxes. When they will be finished I will send them > to the mailing list. >=20 >=20 >=20 > I also experienced some strange things yesterday trying to get things > fixed with regex. Indeed my regex expression was not well formed and it > leads the Devmon to crash. But what surprised me a bit is that there were > no proper clean-up. I had this morning a child which as a 100% cpu > consumption. I am still using the previous version of Devmon, 0-.2.2. >=20 > Can you please fix that? Indeed it, also, appears that regex could crash > when you do not successfully retrieve data from a host. >=20 > Here is what I get: >=20 > Data type mismatch for memTempPer on test.server.com: 'No data' does not > match regex '^[-+]?\d+(\.\d+)?$' >=20 >=20 >=20 > Many thanks. >=20 >=20 >=20 > Etienne Marganne >=20 > TI Automotive. >=20 > The information contained in this transmission may contain privileged and > confidential information. It is intended only for the use of the person(s) > named above. If you are not the intended recipient, you are hereby > notified that any review, dissemination, distribution or duplication of > this communication is strictly prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message. >=20 |