On Sunday, September 28, 2003, at 03:42 PM, Kevin Horton wrote:
I just had a similar thing happen doing a selfupdate-cvs. Nothing was apparently happening in the terminal, but top -u showed the cvs processing using all of one CPU, and the memory requirements growing by the second. I did a control-C to stop the carnage, and tried again and it worked perfectly.
I'm running 10.2.6.
Package manager version: 0.13.7 Distribution version: 0.5.3.cvs
I really hate to be a "me,too" poster, but I had a similar thing happen on my iBook 900Mhz. cvs seemed to be grabbing about 128KB a second and the CPU utilization was fluctuating between 89 and 99 percent. I killed the process and retried 'sudo fink selfupdate-cvs' -- after about 10 seconds cvs exited with an odd malloc error (I didn't think to grab the output, sorry). I tried 'sudo fink selfupdate-cvs' one final time and everything worked fine.
I cannot reproduce this behavior, but I wanted to report another instance "in the wild".
Chip
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
