[1256] in Release_7.7_team
Re: rc.conf variable for default Athena inetd state
daemon@ATHENA.MIT.EDU (Mike Barker)
Wed Apr 15 23:59:22 1998
Date: Wed, 15 Apr 1998 23:55:25 -0400
To: amu@MIT.EDU (Aaron M. Ucko)
From: Mike Barker <mbarker@MIT.EDU>
Cc: release-team@MIT.EDU, "Naomi B. Schmidt" <nschmidt@MIT.EDU>
-There appears to be no optimal way to specify that a machine should
-default to access_on: running access_on from reactivate.local
-introduces a brief window during reactivation in which access is off,
-and changing access_off to access_on in reactivate needs to be
-repeated after a machine is updated. A solution avoiding both
-problems would be to add a variable to /etc/athena/rc.conf to control
-whether /etc/athena/inetd is run with -n and whether reactivate runs
-access_on or access_off.
Hello, Aaron.
I think there may be a misunderstanding about the purpose of access_on
(and access_off). This is intended to be a command used while a user is
logged on to allow other people to telnet into the machine. I.e., it is
intentionally temporary.
If you have a private machine which you want to allow remote access to,
you should be using "mkserv remote". This will set up the machine for
remote access and be preserved across updates.
mike
