comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » SPAWN result
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: SPAWN result [message #93215 is a reply to message #93214] Fri, 13 May 2016 05:10 Go to previous message
khyde is currently offline  khyde
Messages: 21
Registered: November 2013
Junior Member
Thanks for the ideas. I found the easiest thing for me to do right now is check the last line of the log file and if it doesn't start with "Downloaded:" then I know the wget step did not complete.
Kim


On Friday, May 13, 2016 at 7:36:36 AM UTC-4, Haje Korth wrote:
> The result information contains the process ID. Note that on Unix the command must not end with & or the result will be empty. Once you have the process id your can use a spawn to ps, parse the output to check whether the process is alive. Since the spawn process is blocking, you may have to use the IDL Bridge of you want your application to continue.
>
> On Thursday, May 12, 2016 at 9:19:24 AM UTC-4, KH wrote:
>> Hello,
>>
>> I have a wget spawn command that runs every night and is terminated in the morning by another program if it has not finished downloading. What I would like to know is how can I tell if the process completed on its own or was terminated. I've tried including RESULT and ERROR in the call, but they both return empty strings.
>>
>> SPAWN, WGET_CMD, WGET_RESULT, WGET_ERROR
>>
>> Is there anyway to figure out if this job completed or was terminated? I could check the last line of the log file, but I was hoping there was an easier way.
>>
>> Thanks,
>> Kim
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: sqrt in legend() crossing power index
Next Topic: SVDFIT error

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 11:34:31 PDT 2025

Total time taken to generate the page: 0.00371 seconds