in reply to Child Process and SAMBA

Do you get the output from both print statements? Are you sure that script 2 runs?

At the end of script 1, you use open to execute script 2. This should work, but you don't really check. If you really do need to pipe something to script 2, check the open in script 1:

open(TEST, "|$command") || die "Can't pipe to '$command': $!";

If you do not need to pipe anything to script 2, then system would be a more straight-forward way to do what you're trying to do.

if ( 0 != system( $command ) ) { die "system() exited with status $?"; }

Since your code blocks have an extra unbalanced brace in them, I'm wondering if these are part of a larger program and whether you've actually run the test scripts as you've written them here.

Replies are listed 'Best First'.
Re^2: Child Process and SAMBA
by mricci (Novice) on Feb 06, 2008 at 16:11 UTC
    Thanks a bunch for your insight...
    As it turns out after further investigation this does not appear to be a perl issue at all.
    If I attempt to do the same thing locally things work just fine, however going across the SAMBA mount shows the issue.
    I believe that the real problem lies within SAMBA so I am going to research there.. If I find an answer or solution I will certainly post so others that run into this don't have the same problem..
    Thanks again for your insight :)