![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
<geekalert level="mild">
Verily they rock, I ordered my extra 2Gb of RAM yesterday at about 9.30am, it arrived today, and now I have 3Gb in my new PC :-) I also managed to dig out the receipt and stuff for the washer/dryer so it can get repaired on Saturday.
</geekalert>
<geekalert level="high">
I also left work early, because I'd been asked to do a quick recce of the new Unix server we're migrating to at work, just to see if the databases that have been moved over as a test (before they redirect the RAID array and everything else at the weekend) work okay. I expected to be doing this until 5.30 or 6. Naturally the first thing I tried to do was go into the menu script from which the database servers are started. It didn't go well. I got a long list of messages telling me that files couldn't be found.
Now, a little bit about our Unix scripts. They are a bit of a mish-mash, they're ancient (some are 15 years old and probably haven't been changed in that time), and they've also got a lot of checks in there to see if they're running on our own servers, or on a client's. This affects, amongst other things, the setting of certain directory paths. I'd been assured that the new server thought it was the old one (it had been told so, given the same hostname, and so on) so I hadn't expected any of this trouble.
I checked the hostname the server had.
The hostname was 'oakwood'.
The old server is called 'OAKWOOD'.
I configured Apache, made sure it was running okay, then left at 4.30 when it transpired that the tech support manager had already left. (I'd asked for a list of other things to be copied from the old server, in particular the termcap file.)
</geekalert>
Verily they rock, I ordered my extra 2Gb of RAM yesterday at about 9.30am, it arrived today, and now I have 3Gb in my new PC :-) I also managed to dig out the receipt and stuff for the washer/dryer so it can get repaired on Saturday.
</geekalert>
<geekalert level="high">
I also left work early, because I'd been asked to do a quick recce of the new Unix server we're migrating to at work, just to see if the databases that have been moved over as a test (before they redirect the RAID array and everything else at the weekend) work okay. I expected to be doing this until 5.30 or 6. Naturally the first thing I tried to do was go into the menu script from which the database servers are started. It didn't go well. I got a long list of messages telling me that files couldn't be found.
Now, a little bit about our Unix scripts. They are a bit of a mish-mash, they're ancient (some are 15 years old and probably haven't been changed in that time), and they've also got a lot of checks in there to see if they're running on our own servers, or on a client's. This affects, amongst other things, the setting of certain directory paths. I'd been assured that the new server thought it was the old one (it had been told so, given the same hostname, and so on) so I hadn't expected any of this trouble.
I checked the hostname the server had.
The hostname was 'oakwood'.
The old server is called 'OAKWOOD'.
I configured Apache, made sure it was running okay, then left at 4.30 when it transpired that the tech support manager had already left. (I'd asked for a list of other things to be copied from the old server, in particular the termcap file.)
</geekalert>