Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Michael Wojcik wrote: > I don't think Petr said the hostname hadn't changed. He talked about IP addresses changing, but a lot of people get confused when it comes to things like IP addresses, DNS entries (e.g. confusing dotted-IP addresses with hostnames, since most applications treat them equally and just do a lookup to get the host's IP address). > We recently had to update all of our Root files due to server > relocation. The old CVS server is still used for a number of other > purposes, so it had to keep its old hostname. Addressing by name does > not prevent all future issues. There will always be corner cases. > Now, had the old server been originally addressed using an alias (DNS > CNAME) that was used exclusively for CVS purposes, *that* name could > have been transferred to the new server. Exactly. CNAME records make network admin easier, especially when you use them to be used to point to services provided rather than hosts. > (Any problem can be solved by > another level of indirection...) And it gets more fun when you do double-indirection :-) > But the CVS admins didn't think of > that. That is because CVS admins are not network admins. [snip] > (I don't know *why* > anyone would create spacy directories in their CVS repository, but some > of my coworkers have. Sigh.) Never underestimate the crazy things that users will do if left to their own devices.. you could, of course, apply a little bit of magic via some scripts so that users can't do such things. -- David Somers - typographer/programmer/whatever Random (and sometimes useful) stuff blogged at http://www.omz13.com