[3248] in SIPB-AFS-requests
Re: migrating rosebud to a Sun
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Wed Jan 20 15:57:08 1999
Date: Wed, 20 Jan 1999 15:57:01 -0500
From: mhpower@MIT.EDU
To: mwhitson@MIT.EDU
Cc: sipb-afsreq@MIT.EDU, zacheiss@MIT.EDU, hartmans@MIT.EDU
In-Reply-To: "[3247] in SIPB-AFS-requests"
> ... it's not as if a future Athena release could cause us
>to start running services without knowing it.
Right, but a future Athena release might cause programs to be started
with different arguments. For example, it's been common for the
telnetd arguments to change in each release. In general (for machines
that do run inetd), I think the details of inetd.conf are sufficiently
critical that it's best not to have an approach that could result in
them being altered without a human specifically intervening to do so.
The type of human intervention I envisioned was copying the Athena
default inetd.conf into $SIPBTOP/cf whenever a change occurs that we'd
like to have implemented. I suppose another reasonable form of human
intervention is to expect that sipb afs maintainers will somehow pay
close attention to any changes in the Athena default inetd.conf, and
alter sipbops.add if there is a change that we don't want to have
implemented. This seems a bit less safe, in general, but I think it's
ok for now given the number of current sipb afs maintainers who'd most
likely realize when the Athena default inetd.conf had changed.
Matt
