weimer@garden.ssd.kodak.com (Gary Weimer (253-7796)) (04/06/91)
We ran into an interesting problem when changing our machines to use Fully Qualified Domain Names (FQDN). Since the calendar manager (cm) is machine dependant, it needed to be looked at. It turns out that for browse, you can reference name@machine and cm will find name@machine.domain, BUT when giving other users permission to access your calendar, you must enter them as name@machine.domain. This is not a problem, so long as name@machine.domain is not longer than 29 characters. If it is, you have two fixes: 1) when the person desiring to do editing brings up their cm, they must change their hostname to something shorter, start cm, then change the hostname back. (lousy fix and requires root permission to bring up cm) 2) pray that domain is short enough that you can change name and machine such that the three together are less than 29 characters. If you are changing the name (someones login id), you now need rename files in /var/spool/calendar, rename their mail files, and if you're nice, set up aliases so they continue to get mail sent to their old name. If you change their machine name, try not to miss any of the files that you have to change on their machine (/etc/hosts /etc/hostname.??0, /.rhosts--for backups, etc.). Also remember to change the domain name server entry and the entries for all your printhosts, etc. Don't forget to reboot their machine. No go to everyone's account that this person is suppose to be able to modifiy the calendar for. Change their permissions, apply the changes and then REBOOT THEIR MACHINE. Gaads, this has been a fun morning... weimer@ssd.kodak.com ( Gary Weimer )