A beautiful morning...

...though I do have a stiff neck. No matter... it'll go away.

Client U thanked me for my work and said the check went out either Friday or will go out Monday. (That tells me it may have been Friday the 19th, not the 12th.) The end client, apparently, is a slow payer - which I believe - but that doesn't prevent me from getting chapped about not having been paid for a while. I'm noticing that a mid-May invoice is now beginning to smell of old age, too.

Oh, well. It's not worth worrying about; there's not much I can do about it for the moment.

* * *The more I get into PHProjekt, the more I like it, despite various annoyances. I already know that some annoyances can be solved by tweaking the configuration file; the question is: are some of what I consider to be bugs just configuration problems, too?

It'd probably be a good idea to join a mailing list on the subject.

Anyway... daylight is burning. Gotta go.

Cheers...

Careless!

While tweaking the configuration file, I managed to crash the mysqld daemon on 'onegin', but not to the extent that the TCP/IP port was freed up (i.e., restarting the daemon fails because the script thinks there's already one running, as evidenced by the unavailable port).

After struggling some with this problem, I figured the easiest "solution" is what I've learned to do with Windows machines: reboot.

Before rebooting, though, I checked the uptime. It was 114 days, 23 hours, 26 minutes.

Well... at least now the suspense is over and I have a new "longest uptime" to shoot for.

Cheers...

Completely confused...

It turns out I really don't know what happened earlier with MySQL.

The mysqld daemon is now running on 'onegin', but there is no trace of it that I can see in the list of processes on the system.

Even after rebooting, however, I could not connect to the PHProjekt database from any machine on my network. The PHP source was not much help (plus, I am not in a position to be patient). So... I created a new database in MySQL and ran through the setup procedure again. Once finished, I logged into onegin and copied all of the databases from the old database directory to the new one.

What can I say? It worked, and all of my "old" data was still there.

Just for a lark, I called up the configuration file and changed the name of the database to the original name.

It, um, works.

So, I'm thinking that somehow, the previous connection connection got out of synch, which I visualize as a kind of blockage in the pipeline between the server and my computer. Redirecting the attention of the code to a new database I visualize as an operation that forced everything to be reset, thereby unblocking the pipe.

Of course, my visualizations likely have little to do with what actually happened.

Drew and Shannon spent some time this morning looking at houses, and they just stopped by to pick up some things before leaving for Durango to do some serious shopping at the Wal-Mart there. Lee and Galina left a few minutes ago to do a home tour that's being arranged locally.

Cheers...