Path: utzoo!utgpu!watmath!att!rutgers!ucsd!ucbvax!ANDREW.CMU.EDU!cfe+ From: cfe+@ANDREW.CMU.EDU ("Craig F. Everhart") Newsgroups: comp.soft-sys.andrew Subject: Re: WP setup for non AFS sites Message-ID: Date: 16 Nov 89 15:03:04 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 26 Well, you're right in that WP use for non-AFS sites is not well-lived-in. Having a non-AFS override for the WP selection wouldn't be a bad idea. At the moment, the WP is in a conventional location that's supposed to be determined solely by the AFS cell name. What ``ThisDomain'' means is the fully-qualified host name (as opposed to what you might call ``ThisHost,'' which would refer only to the first component of a fully-qualified name, ``apollo'' rather than ``apollo.andrew.cmu.edu''). We try to get the fully-qualified host name by calling gethostname(), then conditionally appending a domain name. If you have the AndrewSetup preference ``ThisDomainSuffix'', we'll append its value to the gethostname() result; if not, and the definition of GETDOMAIN_ENV says that you have a getdomainname() call, we append the result of that call to the gethostname() result. In both cases, the appending is done only if it doesn't appear to have been done already, so (sensible) hosts whose gethostname() call returns a fully-qualified host name won't be bothered by this. At least, that's the intent. I'd argue that you should set ThisDomainSuffix to ``rand.org'' in your AndrewSetup, which then becomes shareable. That doesn't make the WP code try to use the /afs/rand.org/service... path, but it might make you happier in other ways. Craig