[evla-sw-discuss] obs2script
Bryan Butler
bbutler at nrao.edu
Mon Nov 27 11:18:36 EST 2006
wierd. i guess there's no record of which files caused this?
i wonder if it could happen when rich's interface invokes obs2script to convert
a file automatically. rich, any thoughts?
anyway, that's a strange one.
-bryan
On 11/27/06 09:02, Pat Van Buskirk wrote:
> Yes actual running processes, found via top, not via ps. Eva had slowed
> to a crawl, so they looked at top to find out what was going on. They
> found the processes, killed them, and Eva came back to normal.
>
>
>
> Bryan Butler wrote:
>>
>> not in the normal case. were these actually active processes (i.e.,
>> when you say they "found" the sessions running, what does that mean)?
>>
>> when run from the command line, obs2script should always just run to
>> completion. if for some odd reason it got itself into an infinite
>> loop (i've never seen it happen or seen it reported, but who knows...)
>> and the operator left it to run in the terminal, then multiple
>> processes could exist. that seems an odd situation though.
>>
>> might it be that the operator did a %ps -aux or some equivalent and
>> saw processes that weren't actually active (zombies)?
>>
>> -bryan
>>
>>
>> On 11/22/06 08:15, Pat Van Buskirk wrote:
>>> The operators found 7 obs2script sessions running on Eva last night
>>> and wondered if it is not exiting properly when they run it manually.
>>> Is there something special we need to do when it is run manually?
>>>
>>> Thanks for the help,
>>> Pat
>>>
>>>
>>
>
More information about the evla-sw-discuss
mailing list