|
|
Posted by comp.lang.tcl on 11/01/43 11:32
Please see below, thanx!
Cameron Laird wrote:
> In article <1132352850.734347.80770@o13g2000cwo.googlegroups.com>,
> comp.lang.tcl <phillip.s.powell@gmail.com> wrote:
> .
> .
> .
> >> What kind of "user input" does info.php require? When
> >> running info.php on a (Linux?) command-line, do you always
> >> give it the same user input? Is the user input something
> >> like
> >> yes
> >> 14
> >> no
> >> ? Can you automate info.php with the use of a conventional
> >> shell, on the model of such an example as
> >> php -q $root/scripts/info/php/info.php << HERE
> >> yes
> >> 14
> >> no
> >> HERE
> >> ?
> >
> >No, because you will be entering the input yourself via command line.
> >The PHP script itself will prompt you to enter things like your
> >username, password, etc, etc., on the command line, from there you will
> >manually enter the data yourself.
> .
> .
> .
> Ah! Does
> exec php -q $root/scripts/info/php/info.php >&@stdout <@stdin
> get you closer to where you want to be?
Yes it does!! You will have to explain that one to me, though, way
beyond my able to figure it out, but cool!
Problem is that the PHP script contains an exit() function that dies if
user does not input something upon prompting. The TCL script does not
die, it keeps going, which is not the desired effect, but hey I'm
halfway there already, thanx!!
Phil
Navigation:
[Reply to this message]
|