--On Thursday, September 30, 2004 5:58 PM -0400 Ed Ravin <[EMAIL PROTECTED]> wrote:
But you can do it indirectly. Use the "esyscmd" macro in m4:
Ewww.. m4. Uh, I mean, ooh, thats kinda neat. :)
I wonder how well m4/mon handles it when the esyscmd program takes a long time to return, or just fails. I suspect not well, at least during a config reload.
NetSage generates the config files on its own, and then runs a script that copies it into place, asks Mon to test the file, and assuming it passes the test tells mon to reload. An m4 macro that dynamically generates the contents sounds like it would make the 'test and reload' operation both expensive, and unpredictable, since the file would be generated twice, and not guaranteed to be the same.
-David Nolan Network Software Designer Computing Services Carnegie Mellon University
_______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
