This surprised me a little bit: $ du -s -h ~/.sage/temp/jpalmieri/cleaner.log 3.6G /Users/palmieri/.sage/temp/jpalmieri/cleaner.log
Is there any reason to have such a large file lying around? Should it be automatically cleaned up every now and then? Also, I've noticed several times a "sage-cleaner" process which was several days old. That's not supposed to happen anymore. For example, I saw this today: $ ps ux | grep python palmieri 67905 0.0 0.1 2441608 7244 ?? S Sat10AM 59:23.08 python /Users/palmieri/Desktop/Sage_stuff/sage_builds/clean/sage-6.2.rc1/src/bin/sage-cleaner (Note that this was running in a built-from-tarball Sage 6.2.rc1, which certainly contains the fix from #15457.) There were also several hundred directories in .sage/temp/jpalmieri/, with names corresponding to old process IDs, long since dead. Some of these are empty, some have sub-directories with names like "dir_3SAu4B". Shouldn't all of these directories have been removed by sage-cleaner? I have noticed that various Sage processes of mine have been getting killed mysteriously. I wonder if it's an over-aggressive sage-cleaner, seeing an old directory in .sage/temp/jpalmieri and killing a new process with the same pid. For what it's worth, this is on OS X 10.8 (and I think I've also seen it on OS X 10.9). -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
