davidg@aegis.UUCP (Dave McLane) (02/28/91)
I have ISC UNIX System V/386 R 3.2 V2.2 Architech Multi-User but after I install the Multi-User Extension and try and turn on more than one tty with the sysadm; ttymgmt; modtty function, it still gives the message: WARNING: The number of ttys in the "on" state is at the license limit. Before turning on a tty you must first change the state of another tty to "off". However, I can change edit /etc/inittab with vi and turn on more than one tty. There must be a magic something or other someplace. Does anybody know where it is? Thanks in advance, Dave McLane <davidg%aegis.or.jp@kyoto-u.ac.jp>
alexb@cfctech.cfc.com (Alex Beylin) (03/03/91)
In article <m8o5X1w163w@aegis.or.jp> davidg@aegis.UUCP (Dave McLane) writes: >I have ISC UNIX System V/386 R 3.2 V2.2 Architech Multi-User but >after I install the Multi-User Extension and try and turn on more >than one tty with the sysadm; ttymgmt; modtty function, it still >gives the message: > > WARNING: The number of ttys in the "on" state is at the license > limit. Before turning on a tty you must first change the state of > another tty to "off". > >However, I can change edit /etc/inittab with vi and turn on >more than one tty. That is a bug in the sysadm script. I don't recall of-hand what has to be changed to fix it. Warranty Support will give you the fix, if you need it.
davidg%aegis.or.jp@kyoto-u.ac.jp (Dave McLane) (03/04/91)
alexb@cfctech.cfc.com (Alex Beylin) writes: > That is a bug in the sysadm script. I don't recall of-hand > what has to be changed to fix it. Warranty Support will give > you the fix, if you need it. From what I can tell, sysadm is a program, not a script; if it was a script I would be tearing it apart (if I'm wrong please let me know). As for Warranty Support, uhhhh, maybe they could, but I don't know if they will. About the only thing they have done is help me spend my money listening to their recorded message that "you can expect a return call within 24 hours" I'm still expecting.... Actually, that's not quite true, I got through to them a couple of times and they refused to replace the defective disk I have sitting right here on the table in front of me because they said my serial number was for single user. The only way I got the wrong disk (it only has the upgrade for the OS, not VP/ix; luckily that part of the orignal disk was OK) was to have the place I bought it get it for me. I've sent off a request for another disk but, uhhhh, well, what can we say about support like this? So (everybody), please don't send me to the mythical INTERACTIVE Warranty Support; my one month of free "support" was over before I could get them to help me.... --Dave @"I'm not being bitter, I'm just realistic."
sking@nowhere.uucp (Steven King) (03/05/91)
In article <J5DBy5w163w@aegis.or.jp> davidg%aegis.or.jp@kyoto-u.ac.jp (Dave McLane) writes: >alexb@cfctech.cfc.com (Alex Beylin) writes: > >> That is a bug in the sysadm script. I don't recall of-hand >> what has to be changed to fix it. Warranty Support will give >> you the fix, if you need it. > >From what I can tell, sysadm is a program, not a script; if it was >a script I would be tearing it apart (if I'm wrong please let me know). sysadm IS a script on my copy of 2.2, or rather a set of scripts; _/usr/admin/menu/ttymgmt/modtty_ is the actual one that generates that message. It checks the file _/usr/options/.license_ ; it should contain a single ascii char _3_ for the multi-user license. (not that it appears to make a difference for actualy running a multiuser system) >Actually, that's not quite true, I got through to them a couple of >times and they refused to replace the defective disk I have sitting >right here on the table in front of me because they said my serial >number was for single user. The only way I got the wrong disk (it >only has the upgrade for the OS, not VP/ix; luckily that part of >the orignal disk was OK) was to have the place I bought it get it >for me. When I installed my upgrade to 2.2, the multi-user disk developed an error in the midst of the installation and bombed out, leaving me with a partially upgraded system (2.2 but not multi-user). Being rather irratated that I was going to have to go back to 2.0.2 or wait till they replaced my disk, I went ahead and fsck'd it. To my surprise it was able to fix the disk and I was able to finish the installation. -- Look Ma! No .sig! ..!cs.utexas.edu!ut-emx!nowhere!sking
davidg%aegis.or.jp@kyoto-u.ac.jp (Dave McLane) (03/05/91)
sking@nowhere.uucp (Steven King) writes: > sysadm IS a script on my copy of 2.2, or rather a set of scripts; > _/usr/admin/menu/ttymgmt/modtty_ is the actual one that generates that > message. It checks the file _/usr/options/.license_ ; it should contain > a single ascii char _3_ for the multi-user license. (not that it appears > to make a difference for actualy running a multiuser system) Thanks. Somebody sent that to me in mail and I've just posted a summary. > When I installed my upgrade to 2.2, the multi-user disk developed an > error in the midst of the installation and bombed out, leaving me with > a partially upgraded system (2.2 but not multi-user). Being rather > irratated that I was going to have to go back to 2.0.2 or wait till they > replaced my disk, I went ahead and fsck'd it. To my surprise it was able > to fix the disk and I was able to finish the installation. I neglected to mention that I tried that: fsck said it couldn't fix it. Also not mentioned for the sake of brevity is that after I pulled the disk out of the drive I noticed the little round widget that had been cut out of the disk cover for the timing hole was stuck between the disk and the cover. Next time I'll check.... --Dave