On Aug 22, 2013, at 7:31 AM, Alan M. Carroll <[email protected]>
wrote:
> Thursday, August 22, 2013, 2:16:13 AM, you wrote:
>> btw, the only reason I see right now for having an option for passing an
>> additional, configurable parameter to a script, is to use it for sending
>> "instance name" in a multi-instance setup.
>> Question does anyone in our community run multiple instances of ATS on the
>> the same node?
>
> I have to disagree here - if you run multiple instances of ATS on different
> machines it is *very* useful to be able to use the same script everywhere and
> have it vary based on instance data. Having to maintain per machine
> customized scripts is a real pain.
>
The old script provided no such details, did it? The only records.config
configurable portion was the Web UI admin user ("admin"), which is not even a
valid email address on almost every system. That configuration is in fact a
legacy of a feature that was long ago removed.
Having the installed script include a $(hostname) in whatever it sends to the
monitoring service (be it email, SNMP, whatever), seems completely trivial. The
*only* thing that has changed really is that the script doesn't receive the
"admin" string as a command line argument.
I'm with Igor, this is total bike shedding. This damn script is an *example*,
it never worked for 99% of the users, and that one user it did work for can
contact me personally, and I'll fix it for her, for free, when she upgrades to
v4.0.0.
Ciao,
-- leif
