On 7/2/2014 3:19 PM, jmelson wrote: > > On Wednesday, July 2, 2014 2:12:51 PM UTC-5, Charles Steinkuehler > wrote: >> >> so the best way to tell is to run top and see if a bunch of rsync >> processes are chewing up CPU and disk bandwidth. >> > YES, this is it! I DID see three rsync processes running, and was > wondering what the heck they were! I was doing an apt-get install at > the time, and wasn't sure that they couldn't be part of that process, > but didn't think they would be.
Glad to hear that's all it was! > So, the SD card you set up for me at the machinekit meeting does have > the flasher process running on it. And, I suspect that maybe Brad > had the same thing happen to him. I will try to disable it tonight > and see if it fixes the problem. I reviewed my console logs on the netbook, and I did program both the plain and the eMMC flasher version to uSD while in Madison. I suspect I simply got the cards confused. <blush> > So, is anyone who downloaded the machinekit script in the last couple > weeks going to get the same problem? I don't think so, unless I messed up the images instead of just getting confused about which uSD card was which at the meetup. I haven't heard of anyone else having issues other than Brad, and I still think that might have been an errant short (but analysis of the uSD card he was running would show whether he's running the regular or flasher image). -- Charles Steinkuehler [email protected] -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
