Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!zaphod.mps.ohio-state.edu!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!nuug!sigyn.idt.unit.no!hanche
From: hanche@imf.unit.no (Harald Hanche-Olsen)
Newsgroups: comp.sys.apollo
Subject: Re: rgyd keeps dying on my lone sr10.2/dn3500
Message-ID: <HANCHE.90Aug19153625@hufsa.imf.unit.no>
Date: 19 Aug 90 13:36:25 GMT
References: <5067@hemuli.tik.vtt.fi> <JNP.90Aug19005444@mjolner.tele.nokia.fi>
Sender: news@idt.unit.no (Usenet news admin)
Organization: The Norwegian Institute of Technology, Trondheim, Norway.
Lines: 20
In-Reply-To: jnp@mjolner.tele.nokia.fi's message of 18 Aug 90 22:54:44 GMT

In article <JNP.90Aug19005444@mjolner.tele.nokia.fi> jnp@mjolner.tele.nokia.fi (J|rgen N|rgaard) writes:
   In article <5067@hemuli.tik.vtt.fi> Markku.Savela@tel.vtt.fi (VTT/TEL) writes:
	 Everytime this happens I cannot fix the problem from telnet session,
      because I cannot get to root (su says "no permission to su root").
      What is exactly corrupted? And how to fix it that next time rgyd
      dies, I can su root and restart it from telnet session...?

   add yourself to the "wheel" group.

Evidently Markku is already in the wheel group, as he is usually able
to su root.  However, when rgyd dies group information tends to be
unavailable, which is why he can't su root anymore.  Only solutionn (I
think) is to edit /etc/ttys to mark the ptys as secure, then do an
ordinary login as root.  This of course can be a slight security
risk...

A different question is, why does rgyd die?  We had problems of this
kind for a long time, and cured it by making sure that the node
running the master rgyd also ran glbd.  (This solution courtesy of
many helpful people on the net).