As far as I remember, after restart of the server rogue processes have
parent id 1, which makes them easy to identify and kill. Problem of course
being that you need to restart.
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email
On 11/5/11 12:00 PM, William Stein wrote:
On Sat, Nov 5, 2011 at 9:40 AM, Jason Grout wrote:
On 11/5/11 11:37 AM, William Stein wrote:
It certainly seems possible.
I'm restarting the *.sagenb.org servers, since it would be nice for
people to be able to use them...
I already restarted sage
On Sat, Nov 5, 2011 at 9:40 AM, Jason Grout wrote:
> On 11/5/11 11:37 AM, William Stein wrote:
>
>> It certainly seems possible.
>>
>> I'm restarting the *.sagenb.org servers, since it would be nice for
>> people to be able to use them...
>>
>
> I already restarted sagenb.org. I think I've restar
On 11/5/11 11:37 AM, William Stein wrote:
It certainly seems possible.
I'm restarting the *.sagenb.org servers, since it would be nice for
people to be able to use them...
I already restarted sagenb.org. I think I've restarted sagenb.org maybe
2-3 times in the past 2 weeks for this problem