Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!hplabs!hpda!hpcuhb!hpcilzb!johnson From: johnson@hpcilzb.HP.COM (Philip Johnson) Newsgroups: comp.windows.x Subject: Re: xtrek problem Message-ID: <280003@hpcilzb.HP.COM> Date: 18 Oct 88 21:06:49 GMT References: <8810171520.AA28417@ATHENA.MIT.EDU> Organization: HP Design Tech Center - Santa Clara, CA Lines: 10 > But my machines don't seem to know when there is a player on the other > machine. Everybody playing in the same game must start a process on the same machine-- i.e., the xtrek daemon runs on only one machine: everyone forks a remote shell on the xtrek "server." e.g., rsh /users/usr/games/xtrek $DISPLAY & The usual procedure is to use the fastest machine around as the xtrek server. --Phil