I just log this stuff to syslog and let it handle date/time and hostname issues, with the script name as the tag and the pass/fail/whatever as the message. For a lot of shellish scripts, piping to logger works just fine.
-n On Wed, Jul 9, 2014 at 9:15 AM, leam hall <[email protected]> wrote: > I could use some feedback on a thought process. > > Situation: Lots machines (3-4 digit count), lots of scripts on each machine > (100-500). The scripts are identified by a set alphanumeric scheme and the > scripts will either pass, fail, or fix the issue the script refers to. > > Planned output is one file per machine in the following format: > > servername 2017-07-09 scriptID Pass > > The idea is that the relevant outputs can be collated into one larger file > for searching, or input into a database. > > What are your thoughts on this? Ideally others will use this so I'm trying > to think outside my own habits/needs. Feel free to bounce ideas around, you > probably have ideas I haven't even begun to ponder. > > Leam > > > -- > Mind on a Mission > > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ > -- ------------------------------------------- nathan hruby <[email protected]> metaphysically wrinkle-free ------------------------------------------- _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
