On Mon, Dec 03, 2001 at 03:59:34PM -0600, Jamie Seeman wrote:
> print "What command would you like to run: ";
> chomp($command = <STDIN>);
You know. Command prompts are nice and all... What happens when you
want to schedule this with cron, though? Just make sure you first write
your scripts to operate on stdin/stdout w/o any prompting before you
start to think that users need to be led by the choppers in order to get
any work done.
I'd much rather do something like:
bash$ script < infile > outfile
or
bash$ script --file one --file two --file three --file four \
--output blah.log
or
bash$ cat infile | script > outfile
and finally
bash$ script --interactive --verbose
What command would you like to run? blah
Which computers would you like that to run on? computer1 computer3
Would you like that with fries? [y|N] N
That's too bad, fries are good. Oh well. Here's blah.
computer1: B L A H
computer3: error! (see log file for detail)
bash$ echo $?
113
bash$
--
Chad Walstrom <chewie at wookimus.net> | a.k.a. ^chewie
http://www.wookimus.net/ | s.k.a. gunnarr
Get my public key, ICQ#, etc. $(mailx -s 'get info' chewie at wookimus.net)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
Url : http://shadowknight.real-time.com/pipermail/tclug-list/attachments/20011204/5f5e30e7/attachment.pgp