Controlling a child's stdin/stdout (not working with scp)
All,
Ok...so I know I *should* be able to control a process's stdin and stdout from the parent by creating pipes and then dup'ing them in the child. And, this works with all "normal" programs that I've tried. Unfortunately, I want to intercept the stdin/out of the scp application and it seems scp is actively refusing to allow me to. The code is:
I know the code works if I use something other than scp, I can write and read to the pipes all day long and control the process as desired. But, it seems that scp is specifically figuring out what the controlling terminal of the process is and actively refusing to co-operate with my pipes.
I then thought maybe I could try to "disown" the terminal by calling "setsid()" right before invoking scp (and tried it right after the fork). Well, that "works," but then the stupid thing connects to my X server and pops up a box to ask for the password. Of course, preventing scp from asking me anything is the exact reason I want to control the standard in of the process so I can funnel the password in through there.
So...does any one have another idea how I can redirect stdin/stdout for this most difficult process? It seems I'll actually need to "hook into" the terminal directly since scp is "so smart." Indeed, I believe scp may be openning up its own connection to the terminal to get input and send output....
Thanks....
P.S. I know there is a better way to do this, like creating the ssh keys so scp never asks for passwords to begin with. Unfortunately, the environment where I'm trying to use this disallows this. They want us to enter passwords every time and this "stupid" rule is circumventing my ability to automate tasks through scp; of course ftp is also taboo. So...I want this "scp wrapper" to read my local password file and just pass it through so I can get back to my regularly scheduled automation. Otherwise, I'll have to enter the passwords again and again while the scripts run...and that's just...well...pointless.
Hello all, I am trying to create n child processes and control them from a parent process; say make child 3 print its pid and then child 5 do the same and some other stuff. Is there a way to accomplishing this after all the child processes are created via a call to fork().
Thank you,
FG (23 Replies)
Hi,
Program A: uses pipe()
I am able to read the stdout of PROGAM B (stdout got through system() command) into PROGRAM A using:
* child
-> dup2(fd, STDOUT_FILENO);
-> execl("/path/PROGRAM B", "PROGRAM B", NULL);
* parent
-> char line;
-> read(fd, line, 100);
Question:... (2 Replies)
Hi all
I've run into a snag in a program of mine where part of what I entered in at the start of run-time, instead of the current value within printf() is being printed out.
After failing with fflush() and setbuf(), I tried the following approach
void BufferFlusher()
{
int in=0;... (9 Replies)
Hi,
i know how to
a) redirect stdout and stderr to one file,
b) and write to two files concurrently with same output using tee command
Now, i want to do both the above together.
I have a script and it should write both stdout and stderr in one file and also write the same content to... (8 Replies)
Hi,
I am working on a project where I have to generate and execute nasm code on-the-fly. I generate the code in a file program.asm and then execute it.This output is to stdout which i redirect to an output file which i read back to compare results:
system("nasm -f elf program.asm >... (5 Replies)
Hi,
i am using the below program to read from the standard input or to write to standard out put.
i know that using highlevel functions this can be done better than what i have done here.
i just want to know is there any other method by which i find the exact number of characters ( this... (3 Replies)
I am trying to implement the below using Ksh script on a Lx machine.
There is a file(input_file) with 100K records. For each of these records, certain script(process_rec) needs to be called with the record as input. Sequential processing is time-consuming and parallel processing would eat up... (2 Replies)
Well.. let's say i need to write a pretty simple script.
In my script i have 2 variables which can have value of 0 or 1.
$VERBOSE
$LOG
I need to implement these cases:
($VERBOSE = 0 && $LOG = 0) => ONLY ERROR output (STDERR to console && STDOUT to /dev/null)
($VERBOSE = 1... (5 Replies)
Discussion started by: Marmz
5 Replies
LEARN ABOUT PHP
proc_open
PROC_OPEN(3) 1 PROC_OPEN(3)proc_open - Execute a command and open file pointers for input/output
SYNOPSIS
resource proc_open (string $cmd, array $descriptorspec, array &$pipes, [string $cwd], [array $env], [array $other_options])
DESCRIPTION proc_open(3) is similar to popen(3) but provides a much greater degree of control over the program execution.
PARAMETERS
o $cmd
- The command to execute
o $descriptorspec
- An indexed array where the key represents the descriptor number and the value represents how PHP will pass that descriptor to
the child process. 0 is stdin, 1 is stdout, while 2 is stderr. Each element can be:
oAn array describing the pipe to pass to the process. The first element is the descriptor type and the second element is an
option for the given type. Valid types are
pipe (the second element is either r to pass the read end of the pipe to the process, or w to pass the write end) and file
(the second element is a filename).
o A stream resource representing a real file descriptor (e.g. opened file, a socket,
STDIN).
The file descriptor numbers are not limited to 0, 1 and 2 - you may specify any valid file descriptor number and it will be passed
to the child process. This allows your script to interoperate with other scripts that run as "co-processes". In particular, this is
useful for passing passphrases to programs like PGP, GPG and openssl in a more secure manner. It is also useful for reading status
information provided by those programs on auxiliary file descriptors.
o $pipes
- Will be set to an indexed array of file pointers that correspond to PHP's end of any pipes that are created.
o $cwd
- The initial working dir for the command. This must be an absolute directory path, or NULL if you want to use the default value
(the working dir of the current PHP process)
o $env
- An array with the environment variables for the command that will be run, or NULL to use the same environment as the current PHP
process
o $other_options
- Allows you to specify additional options. Currently supported options include:
o suppress_errors (windows only): suppresses errors generated by this function when it's set to TRUE
o bypass_shell (windows only): bypass cmd.exe shell when set to TRUE
RETURN VALUES
Returns a resource representing the process, which should be freed using proc_close(3) when you are finished with it. On failure returns
FALSE.
CHANGELOG
+--------+---------------------------------------------------+
|Version | |
| | |
| | Description |
| | |
+--------+---------------------------------------------------+
| 5.2.1 | |
| | |
| | Added the bypass_shell option to the |
| | $other_options parameter. |
| | |
+--------+---------------------------------------------------+
EXAMPLES
Example #1
A proc_open(3) example
<?php
$descriptorspec = array(
0 => array("pipe", "r"), // stdin is a pipe that the child will read from
1 => array("pipe", "w"), // stdout is a pipe that the child will write to
2 => array("file", "/tmp/error-output.txt", "a") // stderr is a file to write to
);
$cwd = '/tmp';
$env = array('some_option' => 'aeiou');
$process = proc_open('php', $descriptorspec, $pipes, $cwd, $env);
if (is_resource($process)) {
// $pipes now looks like this:
// 0 => writeable handle connected to child stdin
// 1 => readable handle connected to child stdout
// Any error output will be appended to /tmp/error-output.txt
fwrite($pipes[0], '<?php print_r($_ENV); ?>');
fclose($pipes[0]);
echo stream_get_contents($pipes[1]);
fclose($pipes[1]);
// It is important that you close any pipes before calling
// proc_close in order to avoid a deadlock
$return_value = proc_close($process);
echo "command returned $return_value
";
}
?>
The above example will output something similar to:
Array
(
[some_option] => aeiou
[PWD] => /tmp
[SHLVL] => 1
[_] => /usr/local/bin/php
)
command returned 0
NOTES
Note
Windows compatibility: Descriptors beyond 2 (stderr) are made available to the child process as inheritable handles, but since the
Windows architecture does not associate file descriptor numbers with low-level handles, the child process does not (yet) have a
means of accessing those handles. Stdin, stdout and stderr work as expected.
Note
If you only need a uni-directional (one-way) process pipe, use popen(3) instead, as it is much easier to use.
SEE ALSO popen(3), exec(3), system(3), passthru(3), stream_select(3), The backtick operator.
PHP Documentation Group PROC_OPEN(3)