I've tested the object encryption and it isn't at all affected by the new ssl libraries (and their slowness at asymmetric encryption)
Saturday, January 29, 2005
New OFOR files and mchome
MCHOME filled up the four allocated ofor files, so yesterday we added another two. This morning, when it came back up again, it complained about the file versions not matching. Seems that the 2 new files didn't have their CLOSE version set to match the [0] file.
After some investigation - and checking the HEAD code, I've stuck some code in to do so, and tested it (on pyro)
On mchome, I've hacked the startup code to accept the erroneous zero it gets back as a CLOSE version number on the two new files - they've already been created, so I can't do much at this point about setting the correct version number.
After some investigation - and checking the HEAD code, I've stuck some code in to do so, and tested it (on pyro)
On mchome, I've hacked the startup code to accept the erroneous zero it gets back as a CLOSE version number on the two new files - they've already been created, so I can't do much at this point about setting the correct version number.
Subscribe to:
Posts (Atom)