🚀 go-pugleaf

In article <2857@ogccse.ogc.edu>, schaefer@ogccse.ogc.edu (Barton E. Schaefer) writes:
> If you know of a completely portable way (system call or whatever) to
> find out what the domain name *is*, please, please tell us.  I can't
> find a single call (or even a process I could run) that will actually
> tell me what my system's domain name is.  (There's one that is
> supposed to, but it requires YP which we aren't running, and it
> doesn't exist on non-NFS systems anyway.)

Well I don't know of any portable call, but I don't think a "set
domain = ..." call wouldn't be too bad (with .UUCP disallowed :-)).
Then hostname could be prepended (which you already have),
making it less of a job for the system administrator (only
different domains would have to have different setups).  Just a
thought.

>
> Mush relies on the hostname because that's the best it can do by
> itself (at the moment, anyway).  If you tell it your domain name (via
> "set hostname"), it'll use it.

I tried this and came up with some related funniness.  If I set
my hostname to, for example, aecom.yu.edu, and I send a message
to a local user, my autosign2 won't be used even though I have
@aecom.yu.edu in autosign2.  I think it's because the signing
code uses the external "ourname" instead of the value of the
hostname variable.  Maybe when hostname is set ourname should be
set too?  Otherwise, this does seem to do the trick.
-- 
Robert N. Berlinger		    |Domain: naftoli@aecom.yu.edu        
Supervisor of Systems Support	    |UUCP: {uunet}!aecom!naftoli
Scientific Computing Center	    |CompuServe: 73047,741 GEnie: R.Berlinger
Albert Einstein College of Medicine |Pan: berlinger  AppleLink: U0995