On 10/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Ok... this isn't an early haloween scare.
>
> There are two lisp.run processes taking up 100% processor, attached to the
> users jen and jacobml. Those are the only processes under those users, so
> I'm thinking they shouldn't be there. Bug in the cleaner?
The cleaner or any associated code hasn't changed at all in months.
I just tried logging in as jacobml and starting and stopping sage (which
activates the cleaner), and the clisp job under that user was killed.
What happens
is that when you start Sage it checks to see if the cleaner is running, and
if not starts the cleaner. That cleaner stays running until all temp
directories
(for the given computer you're running sage from) are deleted -- i.e.,
the directories that contain sage temp files and keep track of which
processes were spawned by Sage.
Simply restarting sage once fixed the problem, since it caused the
cleaner to run again. This suggests that somehow the user jacobml
explicitly
killed the cleaner. E.g., if a user were to do
killemall python
they would kill all python jobs that they own but nothing else. This would
kill the cleaner but not clisp.run.
So I don't have any idea how those two processes got left running.
If anybody can recreate having processes left running without doing
something like using the OS to kill all python jobs, let me know.
-- William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
