home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!spool.mu.edu!olivea!sgigate!sgi!xingping.esd.sgi.com!arc
- From: arc@xingping.esd.sgi.com (Andrew Cherenson)
- Newsgroups: comp.sys.sgi.misc
- Subject: Re: Is RWHOD working as advertised?
- Message-ID: <tnsabd8@sgi.sgi.com>
- Date: 18 Dec 92 00:32:21 GMT
- Sender: arc@xingping.esd.sgi.com
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 22
-
- In article <34735@adm.brl.mil> ACCESS@krdc.int.alcan.ca (Shawn Allin - Alcan KRDC Computer Services) writes:
- >Recently, we fired up a RWHOD server on our Vax that was ported by Terry
- >Kennedy. We were perplexed at first by the seeming randomness of which
- >machines it saw and which it didn't. I've tracked it down to the fact that
- >the SGI's are broadcasting the information with the fully qualified domain
- >name, rather than just the host name portion as the man pages says it
- >should. This causes the Vax to attempt to write files of the form:
- >rwho.host.domain.name
- >
- >which of couse is invalid under VMS. As I stated earlier, the man pages
- >for RWHOD indicate that it gets the hostname of the machine with
- >gethostname. Here is a quote from the man page:
- >
- > "The host name included is that returned by the gethostname(2) system call,
- >with any trailing domain name omitted."
- >
- >I know that I can probably fix the VMS side to do exactly this, but I'd
- >prefer it to be fixed on the SGI's if indeed it is a bug.
-
- The workaround is not use the FQDN in /etc/sys_id.
- Note that sending the FQDN is useful in networks with multiple domains
- and use rwhod in multicast mode.
-