[326] in SIPB-AFS-requests
rcmd.pit-manager, rcmd.snorkelwacker ID's
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Thu Nov 29 16:34:32 1990
Date: Thu, 29 Nov 90 16:18:54 -0500
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: sipb-afsreq@ATHENA.MIT.EDU
I have added two now user ID's to the protection database for the
sipb cell:
NAME ID
------------------ -----
rcmd.snorkelwacker 65000
rcmd.pit-manager 65001
I added them in that range after talking to Richard and concluding
that it probably would not conflict with other conventions (e.g. UID +
65536 = UID.root). If this is a problem, please let me know.
I am using the ID's to do nightly updates to the FILES and
FILES.look files in the sipbsrc locker. I would prefer to use
snorkelwacker, since it's a sipb machine, but snorkerlwacker is being
hostile to me right now and I don't feel like figuring out why. In
any case, once I have time to convince snorkelwacker to be good, all
it takes to switch it over from pit-manager to snorkelwacker is
dropping a line into the crontab on snorkelwacker, and changing the
acls on the directory that gets modified.
Note that rcmd.pit-manager has write access to only one directory in
sipbsrc, /mit/sipbsrc/src/nightly, so even if somebody decides and is
able to break into pit-manager (unlikely) to wreak havoc on sipbsrc,
the worst they can do is delete the shell scripts in the locker, or
use it to store stuff for a day; not a big deal.
jik
