----- Original Message ----- > 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.
>_o What, exactly, is the difference between having a configuration file (that you create and roll out with your configuration management) for Traffic Server, and an configuration file (that you create and roll out with your configuration management) for a (monitoring) script? scripts, just because they are scripts, don't have to munge data and action. They can be configurable just like everything else. But of course you'd have to write them as such. Anyway. This is starting to dissolve into a bikeshed issue, so I'll excuse myself from this discussion. -- i Igor Galić Tel: +43 (0) 664 886 22 883 Mail: i.ga...@brainsware.org URL: http://brainsware.org/ GPG: 6880 4155 74BD FD7C B515 2EA5 4B1D 9E08 A097 C9AE
