Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!floyd!cmcl2!rna!n44a!wjh12!genrad!decvax!ucbvax!ucbcad!tektronix!uw-beaver!microsoft!fluke!jeff From: jeff@fluke.UUCP Newsgroups: net.unix-wizards Subject: Request for enlightenment re `rwhod' Message-ID: <1405@vax4.UUCP> Date: Fri, 24-Feb-84 13:16:58 EST Article-I.D.: vax4.1405 Posted: Fri Feb 24 13:16:58 1984 Date-Received: Tue, 28-Feb-84 08:08:45 EST Lines: 27 We recently upgraded from 4.1C to 4.2. In the process, the `rwho' program seems to have broken. We have a simple (Ethernet) network of four vaxes. None of these machines are exchanging rwho information with each other. I think they should. A comparison of the code between the two versions of /etc/rwhod shows a considerable change in philosophy. Under 4.1C, the daemon issued broadcast packets once a minute; under 4.2 it appears to speak only to ``neighbors directly connected via a hardware interface.'' I've poked around in /etc/rwhod and discovered that it now speaks only via hardware interfaces of type IFF_BROADCAST|IFF_POINTOPOINT. The ethernet interface meets neither of these tests. Could Someone Who Understands please enlighten me on what the underlying philosophy is here? Is rwho supposed to work among machines connected on a simple LAN? Why did rwhod change so drastically from 4.1C to 4.2? Has anybody made it work for themselves? What's the trick? Jeff Stearns John Fluke Mfg. Co., Everett WA. (206) 356-5064 {uw-beaver,microsoft,sun,teltone,sb1,allegra,lbl-csam}!fluke!jeff -- Jeff Stearns (206) 356-5064 John Fluke Mfg. Co. P.O. Box C9090 Everett WA 98043 {uw-beaver,decvax!microsof,ucbvax!lbl-csam,allegra,ssc-vax}!fluke!jeff