|
From: | Martin Pala |
Subject: | Re: plans |
Date: | Tue, 24 Jun 2003 10:02:37 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030618 Debian/1.3.1-3 |
Christian Hopp wrote:
This could be probably usefull. We have similar problem with alert statements (global alert statement could save lot of space).We could also make global methods.
check ... # method definition section method start "/etc/init.d/apache start" exec on { start } method stop "/etc/init.d/apache start" exec on { stop }With the shortcuts: start "/foo/bar" stop "/foo/bar"
Agree, backward compatibility will be kept:start "/foo/bar" ... can be parsed as: method start "/foo/bar" exec on { start }
Note: it was just example syntax so maybe there are better terms then 'method start "/foo/bar" exec on { start }', what do you think?
Looks good :) It makes the configuration more powerfull (atomic operations for simple events and chaining them for special cases)What do you think, if cpu > 90% then exec method1, method2, method3 makes sense, too? Our language could handle it.
Martin
[Prev in Thread] | Current Thread | [Next in Thread] |