les@chinet.chi.il.us (Leslie Mikesell) (10/04/89)
When running RFS on 3B2's and 386's with starlan it is necessary to use "init 2" to turn off RFS before going to any other state. The network listener is killed immediately when you go to states other than 2 or 3. If you are in state 3 (normal networking) and attempt to go directly to any state other than 2, the effort to gracefully take down the RFS links results in hanging the system since the listener is already gone. Is there some way to avoid this? Les Mikesell
rubin@cbnewsl.ATT.COM (michael.rubin) (10/07/89)
In article <9739@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes: >When running RFS on 3B2's and 386's with starlan it is necessary >to use "init 2" to turn off RFS before going to any other state. >The network listener is killed immediately when you go to >states other than 2 or 3. If you are in state 3 (normal networking) >and attempt to go directly to any state other than 2, the >effort to gracefully take down the RFS links results in hanging >the system since the listener is already gone. Is there some >way to avoid this? > >Les Mikesell It appears to be admdaemon rather than listen that causes RFS to hang. Put all possible init states (0123456) in the inittab entry for admdaemon, and if you're really going to single-user mode, kill admdaemon manually once you get there. It should be fixed in SVR4. --Mike Rubin