Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uupsi!sunic!ugle.unit.no!hanche From: hanche@imf.unit.no (Harald Hanche-Olsen) Newsgroups: comp.sys.apollo,aus.stats.s Subject: Re: Splus dies: "No more processes" Message-ID: Date: 24 May 91 09:30:45 GMT References: Sender: news@ugle.unit.no Distribution: comp.sys.apollo, aus.stats.s Organization: The Norwegian Institute of Technology, Trondheim, Norway. Lines: 34 In-Reply-To: jrm@alpha.ma.adfa.oz.au's message of 20 May 91 02:00:29 GMT In article jrm@alpha.ma.adfa.oz.au (John R Marley) writes: We are trying to run Splus on diskless Apollo 400t workstations, running SR 10.3 psk 8. When we run Splus we get the following output: % Splus Cannot execute UNIX command: No more processes Command was: "echo $SHOME" Terminating because of error in initialization or .First System terminating % We've tried all sorts of things to get it to work, like changing environments or the default shell, but nothing seems to work. A couple of times we've managed to get it to work, but we don't know why. We can run it fine on our Apollo 5500's with SR10.3 psk 8, but these all have disks... Is this a problem with Splus, the Operating System or us? I would guess some combination of the former two. The symptom seems very much like what happens to us when we run the MIT Xapollo (R4) server, or more precisely, when xdm restarts that server after a logout: The server is (often but far from every time) unable to open the screen, and then both the system calls fork() and exec() start to fail -- not only for Xapollo and xdm, but even for unrelated processes like inetd. When failing, the error status from fork() is "No more processes", while if exec() fails the process just crashes. I can e-mail more details if desired (I posted them on comp.sys.apollo a few months back), but frankly I don't think it is going to help. - Harald Hanche-Olsen Division of Mathematical Sciences The Norwegian Institute of Technology N-7034 Trondheim, NORWAY