Hi Scott
Sorry that I didn't reply earlier, I had to go out after sending the message.
The way to check which processes are running is to use the "ps" command. I'm
pretty certain that on a shared host you'll only be able to see your own
processes (but one of the Linux gurus should be able to confirm or deny that).
I ran this script on on-rev:
<?rev
put shell ("ps -aux")
?>
(Yes that is the whole script no HTML).
I got this output:
PID TTY TIME CMD 29690 ? 00:00:00 livecode-server 29694 ? 00:00:00 sh 29695 ?
00:00:00 ps
Which would look like this with linefeeds:
PID TTY TIME CMD
29690 ? 00:00:00 livecode-server
29694 ? 00:00:00 sh
29695 ? 00:00:00 ps
As far as I understand the -aux option to ps should show all the processes
running on the machine but as it is a shared host I only get to see my
processes. The three processes listed are the livecode server, the shell and
the ps command. Which looks fine. If there were any hung LiveCode processes
they would show up in the list.
LiveCode might not terminate properly if a script crashes or goes into an
infinite loop. All you can do is kill the process to clear it (and solve the
bug so it doesn't happen again).
Hope this belatedly helps.
Regards
Peter
PS I saw from your later message that the problem was caused by another user
and is now fixed.
On 23 Apr 2014, at 15:12, Scott Rossi wrote:
> Hi Peter:
>
> How is this check done? The installation of LCserver is on a commercial
> host.
>
> And what would be the process to enable LC to terminate properly?
>
> Thanks for your help.
>
> Scott Rossi
> Creative Director
> Tactile Media, UX/UI Design
>
>
>
>
> On 4/23/14 12:00 AM, "Peter W A Wood" <[email protected]> wrote:
>
>> Hi Scott
>>
>> One thing to check is if the machine has lots of "zombie" LiveCode
>> processes just in case LiveCode is not terminating correctly.
>>
>> Regards
>>
>> Peter
>>
>> On 23 Apr 2014, at 14:02, Scott Rossi wrote:
>>
>>> Hi LC Server Gurus:
>>>
>>> One day after getting an LC server-based form working, the response time
>>> of the server has suddenly decreased substantially. I put up a simple
>>> one
>>> line script that returns the long time, and here it takes between 20 and
>>> 30 seconds to execute. A simple HTML page with "hello world" responds
>>> immediately.
>>>
>>> Is it possible that my repeated requests during testing have "stacked
>>> up"
>>> and bogged down the server? Is there some kind of reset and/or
>>> maintenance
>>> thing I can do?
>>>
>>> Everything appeared to be running fine yesterday, but today things are
>>> unusuable.
>>>
>>> Thanks for any suggestions.
>>>
>>> Regards,
>>>
>>> Scott Rossi
>>> Creative Director
>>> Tactile Media, UX/UI Design
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> use-livecode mailing list
>>> [email protected]
>>> Please visit this url to subscribe, unsubscribe and manage your
>>> subscription preferences:
>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
>>
>> _______________________________________________
>> use-livecode mailing list
>> [email protected]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
