kerr@OODIS01.AF.MIL (Grant Kerr) (10/15/89)
> Has anyone seen the message: > rlogind: /etc/init: Invalid argument when trying to rlogin into a Pyramid? > It seems to be an intermittent problem. > > We seem to have plenty of pty's left (the higher numbered ones have > access/modify times of about 1 year ago). > > Pyramid was not able to tell us what the message means. Below is part of the README for the PTF we installed to fix the intermittent invalid argument problem... grant (kerr@oodis01.af.mil) # nsp Software Package OSx 4.4 with special fixes for SPR 4983 PRODUCT: nsp_4983 PRE-REQUISITES/DEPENDENCIES: Requirements: OSx 4.4, Standard March 1989 PTFs FIXES: FIXES: /etc/rlogind (44.1.1.1) /usr/etc/intenetd (44.1.1.1) jwang spr 4983 The rlogind and telnetd set the catch for the SIGCHLD after the fork which allow for the child to die before they set the catch. ################################ May 5, 1989 ############################## etc/rlogind (44.1 BEIN) usr/etc/in.telnetd (44.1 BEIN) usr/sys/kernel/syslib.a (BEIN) usr/sys/kernel_m/syslib_m.a (BEIN) dbyle for bein SPR 4983 The above two daemons and two libraries are inter-connected and require each other to work properly. They include a special change documented in SPR 4756. The daemons will NOT work with a kernel that does not have the above libraries. The system should also have the April 1989 PTFs for osx, nsp & nfs. ################################## 9 May 1989 ############################ io/devinit.c (5.11 BEIN) dbyle for bein SPR 4983 sys/kern_descrip.c (44.3 BEIN) sys/kern_exit.c (44.4 BEIN) sys/kern_fork.c (44.2 BEIN) usr/sys/kernel/iolib.a (BEIN) usr/sys/kernel/syslib.a (BEIN) usr/sys/kernel_m/iolib_m.a (BEIN) usr/sys/kernel_m/syslib_m.a (BEIN) New facility for /dev/init which marks the login process so that it automatically unlogs itself as it exits. ################################## 11 May 1989 ############################ etc/rlogind (44.1 BEIN) dbyle for bein SPR 4983 usr/etc/in.telnetd (44.1 BEIN) Cleaned up versions of these daemons to work with new automatic unlogging code from previous fix dated May 11. ################################## 12 May 1989 ############################ NOTES/WARNINGS: ***************** *** 12/15/87 PLEASE NOTE: *** When a ptf is installed using the *.README installation script, a file is created (or updated) on the system. This file is located in /usr/PTF directory and is called 'PTF.log'. This file will contain: the name of the ptf, the date the ptf was installed and the contents of the *.ONELINE description of the ptf. Also, the last ptf to be installed will be the first entry in the file, and the oldest ptf installed will be the last. ############################################################ WARNING: This requires the corresponding OSx Special PTF! Also - BE SURE TO SAVE THE CURRENT DAEMONS AS THE ONES IN THIS PTF ARE INCOMPATABLE WITH ANY OTHER KERNEL!!!!!!! ################################################################ CONTENTS: -rwxr-xr-x 1 bin 61440 May 12 11:02 ./etc/rlogind -rwxr-xr-x 1 bin 69632 May 12 11:07 ./usr/etc/in.telnetd
mike@blia.BLI.COM (Mike Ubell) (10/16/89)
Has anyone seen the message: rlogind: /etc/init: Invalid argument when trying to rlogin into a Pyramid? It seems to be an intermittent problem. We seem to have plenty of pty's left (the higher numbered ones have access/modify times of about 1 year ago). Pyramid was not able to tell us what the message means.
csg@pyramid.pyramid.com (Carl S. Gutekunst) (10/16/89)
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. <csg>
chris@yarra.oz.au (Chris Jankowski) (10/16/89)
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. > > We seem to have plenty of pty's left (the higher numbered ones have > access/modify times of about 1 year ago). > > Pyramid was not able to tell us what the message means. Well, I am also Pyramid but I had this one before. (:-)) On the system I had this problem it was caused by somebody modyfing an entry for a pseudo terminal in /etc/ttys on the target (remote) system from say 02ttyp9 to 12ttyp9 (logins enabled). The intermittant nature of the problem is then obvious. If there is less then 9 pseudo terminals in use everything is OK. Next one gets rejection. Could you let me know if that was your problem? -m------- Chris Jankowski - Senior Systems Engineer chris@yarra.oz{.au} ---mmm----- Pyramid Technology Corporation Pty. Ltd. fax +61 3 820 0536 -----mmmmm--- 11th Floor, 14 Queens Road tel. +61 3 820 0711 -------mmmmmmm- Melbourne, Victoria, 3004 AUSTRALIA (03) 820 0711 For every idiot-proof system, a new improved idiot will arise to overcome it.
frank@ntc.UUCP (Frank Schulz) (10/17/89)
I see the rlogin problem about once a week. I reboot and the problem goes away for a random amount of time. In fact, as I write this article, a user comes up to me and complains about rlogin. About the time the rlogin problem occurs, the /etc/utmp entries tend to get mangled. Probably time to upgrade my OS to a current release. I am on TOS3.3.03 which is OSx4.4.??