|
|
Removing an autoinstalled machine from DCS support
How to remove an autoinstalled machine from DCS support:
First, make sure the PI knows we're going to do this stuff Before doing it.
You don't necessarily need to go down the list with them, but a quick call to
say "we'd like to shut off various remnants of the DCS support structure on
your machine, is that ok?" beforehand is very important.
- Switch the machine to NONE support in the database. Don't forget to
eliminate backups too, if they don't want that either anymore.
- Ensure ~root/.forward doesn't send mail to DCS anymore.
- Talk with the PI's of NFS servers to see if it's ok to continue exporting
filesystems to the machine. Try not to imply that anything that isn't
supported by DCS will instantly be broken into. If you don't export the
mailspool to it anymore, don't MX it either and remove it from hidden.hosts.
- Edit root's crontab and remove any jobs that might send mail to dcs.
- Check .../rc3.d/* for things that might send mail to dcs, and eliminate
them.
- Let the owner of the machine pick one of these options:
- Leave the machine as it is, with dcslib dependencies.
- Reinstall the machine and leave it. No configuration unless they pay
hourly.
- Remove dcslib dependencies hourly
- Remove the dcs and consult accounts. Don't just render them unusable;
actually get rid of them so there's no question we can't use them
anymore
- Change /etc/syslog.conf so the machine doesn't log to loghost.acs
anymore
- touch /.nosrsh
- remove the host from the srsh database with ./srsh -r on bounce2.nac
- Remove machine from netreo
|