Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!ames!lll-lcc!pyramid!csg From: csg@pyramid.pyramid.com (Carl S. Gutekunst) Newsgroups: comp.sys.pyramid Subject: Re: rlogind: /etc/init: Invalid argument Message-ID: <87831@pyramid.pyramid.com> Date: 16 Oct 89 05:57:10 GMT References: <9714@blia.BLI.COM> Organization: Pyramid Technology Corp., Mountain View, CA Lines: 19 In article <9714@blia.BLI.COM> mike@blia.UUCP (Mike Ubell) writes: >Has anyone seen the message: "rlogind: /etc/init: Invalid argument" when >trying to rlogin into a Pyramid? It seems to be an intermittent problem. This was a timing problem between rlogin and the child process it forks to accept the call. Pyramid uses a magic device, /dev/init, to do the universe- specific processing of login. (Writing the two utmp files, wtmp files, etc.) I've forgotten the exact bug, but it had something to do with the child doing the write to /dev/init when the parent should have, or vice versa.... Anyway, it's certainly fixed in OSx 5.0, along with porting the 4.3bsd-tahoe versions of the networking daemons. I'm not surprised that RTOC didn't know about it, since I'm pretty sure, um, I, er, *forgot* to put this fix in the OSx 5.0 NSP Release Notes. (The bug was actually fixed by our tty wizard. I ended up doing the Release Notes based on the who-touched-it-last rule. :-)) The problem is pretty harmless. Just do the rlogin again.