Read the first part of my original email where swatch can launch script2 directly and it will work when I tee the output but fails without piping the output to tee. This makes me think that it's something related to the timing or relationship of the child process spawning by the sftp code. Also, if you Google this error message, you will see that someone had the same problem launching sftp from SAP via a script. So it doesn't seem to matter what is launching the sftp command but there has to be something in common. Dave On Wed, Mar 3, 2010 at 3:00 PM, Dominik George <nik@xxxxxxxxxxxxx> wrote: > Look at what exactly swatch spawns. Script1 will spawn a shiny new shell > for script2, swatch probably doesnt. > -- > Sent from my Android phone with K-9 Mail. Please excuse my brevity. > > > "Dave Jones" <davejones70@xxxxxxxxx> schrieb: > > >RedHat Enterprise Linux 5.3 > >OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008 > > > >I am using swatch to monitor the vsftpd log and the secure log for FTP > >and SFTP inbound transfers then trigger a script to send the file > >outbound. When I use the sftp command to send a file outbound, I am > >getting "Couldn't wait for ssh process: No child processes" with a > >return code of 255. Here's the strange thing: > > > >swatch -> script2.sh -> sftp command -> fails with RC 255 > >swatch -> script1.sh -> script2.sh -> sftp command -> successful with RC 0 > >swatch -> script2.sh -> sftp command piped through tee -> successful with > RC 255 > > > >Script1.sh is just a simple script that calls script2.sh with the same > >arguments that swatch passed from the log line.
