Here is the result of ps, which I forgot about: PID TT STAT TIME COMMAND 22503 p1 S 0:00.04 -bash 23320 p1- S 9:50.62 python /Users/.../sage-4.1.2.rc1.alpha3-copy/ local/bin/sage-cleaner 5846 pb Ss+ 0:00.03 bash /Users/.../sage-4.1.2.rc2/sage -python - u 5853 pb S+ 0:00.04 bash /Users/.../sage-4.1.2.rc2/local/bin/ sage-sage -python -u 5865 pb S+ 0:00.09 python -u 3113 pc Ss+ 0:00.03 bash /Users/.../sage-4.1.2.rc1.alpha3-copy/ sage -python -u 3120 pc S+ 0:00.04 bash /Users/.../sage-4.1.2.rc1.alpha3-copy/ local/bin/sage-sage -python -u 3144 pc S+ 0:00.08 python -u 5593 q0 Ss 0:00.03 bash /Users/.../sage-4.1.2.rc2/sage -twistd --pidfile=tmpO_Yq8b/twistd.pid 5600 q0 S 0:00.04 bash /Users/.../sage-4.1.2.rc2/local/bin/ sage-sage -twistd --pidfile=tmpO_ 5614 q0 S 0:07.65 python /Users/.../sage-4.1.2.rc2/local/bin/ twistd --pidfile=tmpO_Yq8b/twis 2860 q1 Ss 0:00.03 bash /Users/.../sage-4.1.2.rc1.alpha3-copy/ sage -twistd --pidfile=tmpRsQnL 2867 q1 S 0:00.04 bash /Users/.../sage-4.1.2.rc1.alpha3-copy/ local/bin/sage-sage -twistd --p 2880 q1 S 0:07.93 python /Users/.../sage-4.1.2.rc1.alpha3-copy/ local/bin/twistd --pidfile=tm
Note again that on this computer, Sage hasn't been run (and, afaik, was closed properly) in at least a week. And certainly sage-4.1.2.rc1/2 hadn't been run for months! Maybe it was a problem specific to those - or a bad termination of them? In which case I apologize for wasting bandwidth. But if someone knows what I did wrong, hopefully I can avoid doing it in the future, and maybe we can put a check in for it if people are similarly unlucky. - kcrisman On Feb 2, 10:32 am, kcrisman <[email protected]> wrote: > Dear support, > > Has anyone ever had the following problem on Mac? I get this on both > PPC and Intel. > > One has some Sage installations. One builds/downloads new ones. One > puts the old ones in the Trash, and then tries to Empty Trash. Then > one gets a whole bunch of messages like: > > "The operation cannot be completed because the item libpari-gmp.dylib > is in use" > > Also for many .so files like real_lazy.so, and even python and sage- > sage. Note that in these cases Sage has not been in use for many hours > or even days, and the Terminal is closed. > > I've deleted these now, so I can't reproduce it again, but it did > happen twice, which maybe counts. > > Are there processes running in the background that never stop, even > after Sage is terminated? I only know how to use top very naively, so > I didn't see any processes that seemed suspicious. Anyway, if there > are, that would seem to be bad. > > - kcrisman -- To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
