On Wed, 2010-03-03 at 23:44 -0500, Dale Worley wrote: > On Wed, 2010-03-03 at 22:48 -0500, Scott Lawrence wrote: > > On Wed, 2010-03-03 at 21:43 -0500, Dale Worley wrote: > > > tar -x --to-stdout -f snapshot.tar.gz > > > ./var/log/sipxpbx/sipXproxy.log >/tmp/file1234 > > > analyze_483s /tmp/file1234 > > > > > > > Then why can't that tar command and that temp file be inside the analyze > > script? > > It certainly could be done. But in regard to the philosophy of making > tools, I wrote one tool to process a log file to find loops, etc., and > left it to the user to determine how he wanted to obtain the log file to > be processed. In a similar way, "wc -l" counts the lines in a file, and > one could incorporate into it extracting an element of a tar file whose > lines should be counted. But it would be an odd marriage of > functionality, for sure.
I couldn't be more in agreement with you philosophically _if_ we were creating tools for Unix users, but we're trying to create tools for ordinary people, and that implies the need for an extra level of packaging. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
