Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Capture command line output directly to a text file' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Capture command line output directly to a text file
Authored by: Cerberus on Jul 29, '08 02:00:11PM

I think the primary consideration for NOT doing this is that you would then have to go and delete this file once you were done with it. By using a file stored in /tmp it is automatically deleted after 3 days.

But otherwise your point is valid.

And to argue AGAINST my own statement then your command could make the file in /tmp/* fashion.

OK, Base fact is that I think this tip works well due to its simplicity. If I don't care about the file (or file name) and do want the data then piping the output to 'open' would be more than acceptable and the system cleans up the resultant debris and I don't need to care about the initial file name or its location. Remember, there is potentially THOUSANDS of ways to skin data in *NIX.

[ Reply to This | # ]