Reformatted excerpts from Edward Z. Yang's message of 2009-06-03: > Somehow, I messed something up really bad, and now, whenever Sup > attempts to poll for new messages, it hang completely, spinning the > CPU. I've let it run for an appreciable amount of time, and haven't > seen any change. I was wondering how I could fix this, or go about > debugging it.
Is the curses interface hung? If not, can you see if there's activity in the poll mode or the log mode buffers? (Hit ; if you're running from git, or B if you're running 0.7.) It might be that you've somehow reset the recorded offset for a very large source, so Sup is polling a lot of stuff in the background. If it's completely hung (which would be weird), try first disabling your hooks (move them from ~/.sup/hooks to another directory) and see if that helps. If not, please describe the behavior of running sup-sync. -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
