I haven’t been posting much lately because I’ve been drilling away on a paper that’s due Monday. I’m taking a few minutes now to destress before I catch some sleep, then it’s back awake tomorrow to work some more. I think I’ll be ok time wise, but it’s been a while since I was conditioned to working like this (yeah, I’ll admit it, I kinda miss school a bit at times like this).
Anyway, only had one thing worth writing about now (more Tuesday after I’ve had a chance to catch up on sleep). It’s all fun and games when you’re writing code for internal use only and you call something “Tard.C” (It’s a tarpit daemon, therefore following unix convention it’s… tar-d). Then of course, what can you do when you’re writing a paper on the subject but leave the name? I mean, it really is the unix convention, so I guess I’ll just pretend we didn’t notice the alternate interpretation. It actually gets worse, too. The server running tard was called “Sticky”. Official dns, and everything. Believe it or not, it’s all very plausible and legit, but it was worth a few inside chuckles at the time.
Suppose Tard.C daemon crashes; what’s it called when it’s invoked a second time?
Left by 2cool2tell on September 19th, 2004
Wow.
Totally hadn’t even thought of that. Bloody brilliant.
Actually, tard was invoked by xinetd. So really there were hundreds of tards running (around?) at the same time. If one tard crashed, you didn’t mind because there were as many tards as needed to handle the next connection. Power in numbers.
You can tell we had a lot of fun with this.
Left by Jordan on September 19th, 2004
lol
tards…
running (around?)
at the same time
!
…If one tard crashed… {laughs immaturely}
Left by David on September 23rd, 2004