On Mon, Dec 7, 2009 at 1:19 PM, Brian Cuttler <[email protected]> wrote: > I may have missed the boat, but why not have a smarter script. > You should be able to write code that when run remotely by ssh > (or rsh or...) that can tell what the current host is and perhaps > 'do nothing' if its not the target system, or if carefully written > check state files that the script writes, in, oh, /tmp/amanda on > the client, to determine what phase or state/step is required of it.
I'd hate to see too much work go into hacking *around* the script API -- it's brand new! The best outcome would be to fix/improve the script API as appropriate, but at the very least, let's make sure that the limitations of the API are well-documented. From what I can tell from this thread: * per-host scripts can only run on the server * per-host scripts run for *every* DLE to which they are attached, which can result in them running several times for a single host; even in this case, all scripts are run before any hosts are dumped Did I miss anything? Dustin -- Open Source Storage Engineer http://www.zmanda.com
