Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!lll-lcc!ames!ll-xn!husc6!cmcl2!brl-adm!adm!cew@venera.isi.EDU From: cew@venera.isi.EDU Newsgroups: comp.unix.wizards Subject: Ultrix32m 1.1 on MicroVaxII Message-ID: <7539@brl-adm.ARPA> Date: Tue, 26-May-87 16:18:32 EDT Article-I.D.: brl-adm.7539 Posted: Tue May 26 16:18:32 1987 Date-Received: Wed, 27-May-87 05:04:11 EDT Sender: news@brl-adm.ARPA Lines: 39 Greetings! I am running into multiple problems with a MicroVaxII currently running Ultrix32m v1.1. I hope to get some useful suggestions from the list. First problem: the kernel keeps writing "Login limit reached" to /usr/adm/messages. I have a hard time believing this because it usually just has one user (me) on it. This problem is interfering with the operator backups. The kernel is configured for 32 users (was 16). Any ideas what this really means? The next problem deals with MMDF mail daemons: they fail to startup on reboot. The echo messages from rc.local do state that the mmdf daemons are starting, but they are never there when I login. They startup fine from the root command shell. (Could this cause the "Login limit" problem above? These processes are associated with a tty.) I don't intend to stay with Ultrix 1.1. Does anyone have any experience with 4.3bsd or Ultrix 2.0 on mVaxII's? I have tried building a 4.3 kernel from our Mt. Xinu 4.3 distribution but these kernels will not come up single-user. (Mt. Xinu seems to be missing one driver (device qv -- isn't that the console monitor?). Are there substitutes?) To reiterate, my current choices are Mt. Xinu 4.3bsd or Ultrix 2.0. I would certainly be interested in hearing the pros and cons of both (or even other alternatives). Thanks, Craig ============================================= ARPA: cew@venera.isi.edu PHONE: (213)822-1511 ext. 111 USPS: USC Information Sciences Institute 4676 Admiralty Way, Suite 1100 Marina del Rey, CA 90292 Slogan: "nemo me impune lacessit" =============================================