Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I'm helping to sort out an ancient Intergraph 6800 machine at work, running CLIX, a proprietary Unix.

Binning the system is not an option. It is a certified safety-critical system that would cost $millions to replace. Please do not post suggestions that the system could be replaced as it is utterly infeasible to do so, even if the problem detailed in this posting cannot be addressed.

Recently the hard-disk died so (before I was involved) the OS (1999 vintage) was installed on a new hard disk. A recovery company got all the files off the old hard disk and most of my involvement has been copying applications and data off the CD supplied by the recovery company and setting ownership and permissions correctly on the fresh installation.

One point however is that the system used to allow at least six users to log in but now if more than two do, /bin/login says:

Too many users logged on.
Try again later.

Those strings are in the /bin/login executable.

The system does use a licencing system and I suspect that a crucial licencing file is missing from the fresh installation. I'm sure it will be on the recovery CD but does anyone with knowledge of these old licencing systems have any suggestions about where the files are so I can copy them across from the CD ?

PS, if anyone has a licence for Intergraph NFS that they want to liquidate, we might be interested.

share|improve this question
6  
Binning the system is always an option. It just might cost money. The question is whether it will cost more money to keep it running than to replace it. –  Michael Hampton Jan 17 at 10:23
1  
What was the point of that comment ? –  Michael Jan 17 at 10:47
1  
Its a comment. The point of it is to put across something unsuitable to being an answer. While I suppose these systems were built like a brick outhouse, at some point, something you can't find a replacement for may break, or you simply may no longer have the folk who remember how these things are fixed. Someone may know the answer to your immediate problem, but this is something any sysadmin keeps in mind on the longer term –  Journeyman Geek Jan 17 at 10:51
1  
@Michael Correcting a factual error? The truth? Adding information? Lots of good reasons for that comment. I mean, good luck with getting a proper answer you can use, but Michael Hampton's comment is accurate and valid. To add to it, I'd point out that you're trusting your safety to a piece of software that's legally old enough to drink. Would not make me feel remotely safe. –  HopelessN00b Jan 17 at 10:51
1  
What they said. Seriously, I do wish you luck in solving this, but I suspect you're going to be waiting a long while. When I tried to Google this, I got referred to an archaeologist...I suspect the same happened to you. –  Michael Hampton Jan 17 at 10:53

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.