01:54 pm - Glitches
First, because it's a question that I don't want overlooked at the end of the rest of the text: I forgot to change my InsaneJournal syndication settings last night to not post complete entries to the syndicated feed of my IJ account over at LJ (intended as a temporary change just for the day). I tried to take care of that just now but cannot find the page on which to make the change. Er ... can anyone help me out here?
Anyhow, on to what I was thinking about just before that:
Huh. The modification I made to my client last night doesn't agree with CrazyLife for some reason (which is why my QotD didn't post there at 5:25 this morning -- I just posted it manually using the previous version of the client (glad I renamed it instead of just writing over it!) after noticing that my most recent entry had failed there. I wonder what the problem is. (It's reported as "problems logging in", which is odd considering that the edit I made was not in the login module. The error-reporting may be off.)
Because I've been too lazy yet to hack Clive (the client I use) to crosspost automagically (I do have a plan[*] for that, but ...) I've got nine copies of the executable instead, each aimed at a different site, and I invoke them each from within a foreach() loop (I'm a csh/tcsh users). As a side effect, this made it easy to strip LJ out of the list of sites to crosspost to today: all I had to do was 'mv ljclive ljclive.real ; cp dummy ljclive' (dummy is a program that does nothing -- void main(){} -- that I've found surprisingly useful over the years). In order to automate the trick where this morning's quote-of-the-day was posted to LJ as a fake cut-tag linking to the InsaneJournal copy, I had to make a wee change to the InsaneJournal client so that instead of reporting success with the message, "Successfuly posted item [ITEMID] to InsaneJournal," it would report the URL of the entry it had just posted. (When I get a round tuit, I'll add a command-line switch to choose at run time between reporting the itemid or the URL on success.) Wanting to keep my computing environment a wee bit more tidy than my house (uh, actually, I fail in both places, but never mind), I went ahead and recompiled all the clients to have their code in sync. Hence the CrazyLife glitch which I'll need to debug later.
Of course, I completely forgot the reminder in the motd here, pointing out that my ISP upgraded the host I usually log in on to a newer version of NetBSD than the other hosts available to users and that programs compiled on this one might not work on the others ... and that cron jobs run on one of the other hosts. Luckily, despite my attempts to the contrary, I was still awake when the QotD script ran, eventually noticed that it was stuck, and recompiled the nine clients on the right computer and ran the script again by hand. (Which is why today's QotD showed up at 5:55 instead of 5:25.) I did test things beforehand, of course, but, you guessed it, I tested them on the wrong machine. I blame poor sleep. (Why yes, that is an awfully convenient excuse, but that's my story and I'm sticking to it.)
So: glitchitude. But relatively minor stuff, annoying but easily worked around until I figure out how to fix it properly, or in the case of the compiled-in-the-wrong-place problem, trivially repaired. But not the completely smooth operation I'd hoped today would appear to be.
And I thought I had a similar problem with CommieJournal, but apparently that entire site is down today for maintenance/upgrade/something. (Maybe not the best timing for that, but if something broke and they had to fix it, oh well.) I'll try to remember not to overwrite the text files containing today's entries as I compose each next entry, to make it easier to post 'em all to CommieJournal once it comes back up.
And the Blurty client is reporting failure, but my entries are showing up there. Hmm.
Okay, now to go take care of those errands ...
[*] Actually three different plans. My question a few days ago about whether anybody else still uses Clive was to help me decide which plan to use.