scripting suggestion: how to make this command shorter
zhangweiwu at realss.com
Sat Jun 27 16:17:17 UTC 2009
> Perhaps you could put it into a text file and have cron simply execute
> the text file. By doing so, you are free to break it up into a more
> digestible format and start using programming constructs to make your
> life easier. (Such as storing values in variables, or processing
> standard input so the script can be called with various URL's and so
> forth.) Your cron job could then simply execute "/home/you/bin/foo",
> where 'foo' is whatever you decide to name the script.
> Is there any specific reason why this has to be all on one line?
Nothing more than curiosity and small benefit of not having to take care
one more file. I know what you mean:)
More information about the freebsd-questions