And naturally, the next book I pick up has, as a character, what's basically my archetype of the Girl I Want Most - someone who I've come close to finding a few times, but have never managed entirely.
And then the author decides to kill her off.
*SOMEONE* up there is having a great time with all this, I can tell.
So I've got this plane ticket - I'll be coming in on May 10 (Saturday), at 5:40 PM, and leaving on Wednesday at *wince* 7 AM.
This is where I need to do a ton of planning >_<
With luck I'll have a driver's license and will thus be able to rent a U-Haul van and truck my stuff to a storage facility. With lack of luck, I won't. I can get myself back and forth to Oberlin via taxi if need be, but that won't help me move stuff. So - anyone know someone who's willing to help me cart some stuff to Cleveland in the worst case? I'm (obviously :P) willing to pay for van rental, gas, etc, but if I can't drive it all gets rather nastier.
So: driving that would be appreciated: back and forth from airport, back and forth to Cleveland for storage. Donations of time appreciated, but if you want to be paid, I'll do it, especially for the storage run ;)
(Oh, and yes, I've checked - U-Haul will rent to people as young as 18.)
On a less business-like note, it'll be good to see those of you who are still there again ^^
Question for those techs out there.
I'm trying to set up a "load" indicator for this distributed computing server. The way Windows does their load indicator is to simply read off the amount of CPU time that's being used. I could do that easily (the percentage of available CPUs that are being used) but my load would end up being either 100% or 0%, very rarely ending up in between.
Linux, on the other hand, calculates load as the number of processes, on average, that are waiting for a timeslice. 0.03 means 3% load, 1.00 means one process is eating all the time, and the handy thing is that this continues going above "full load" - 7.00 means there are seven processes all attempting to get the entire processor. Or both processors.
Unfortunately this fails rather miserably also, since one "job" could easily eat four hundred processors if they were available, but that much work existing doesn't really have anything to do with the load - a single four-hundred-processor job, once a week, is pretty low load, since it'll spend most of its time idling. However, one every few hours would be extremely high load - in fact, it would end up falling behind.
So . . . suggestions? I guess I just want an easy way of monitoring how much the network is doing, with it being able to tell me "I am precisely x% overworked" or "I am x% idle" without any problems, and I'm having trouble coming up with one :P
Questions welcome, incidentally. I haven't gone into much detail on this ;)
When you cut a bagel in half, spread cream cheese on it, and eat it . . . then remember that it's traditional to put the halves *back together* before eating the half you put cream cheese on.
At least I've got leftover cream cheese to go with my half a bagel.