Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!purdue!bu.edu!xylogics!world!madd
From: madd@world.std.com (jim frost)
Newsgroups: comp.unix.wizards
Subject: Re: Local daemon socket
Keywords: tcp-ip sockets SOCK_STREAM
Message-ID: <1990Mar8.010734.24165@world.std.com>
Date: 8 Mar 90 01:07:34 GMT
References: <1990Mar07.023424.2875@csuchico.edu>
Organization: Saber Software
Lines: 20

warlock@csuchico.edu (John Kennedy) writes:
>  I'm looking for a way to make a daemon executable on more than one machine.
[...]
>  If I only have one daemon running on the network, it's fine.  If I have two
>or more, they fail to bind the socket (Address already in use).  I'd like to
>limit the daemon so that other daemon's may be run on different host machines.

It doesn't look as though it should fail if run on different machines,
only if run on the same machine.

I can't give you any advice as to what's the matter with your code,
but I *do* have a tutorial with code fragments that show how to
properly set up an AF_INET SOCK_STREAM server/client pair and to
communicate between them.  I also have a full application -- a network
message system like "rsend" -- which I could send to you as a further
example.  Interested?  If so, please contact me via email.

jim frost
saber software
jimf@saber.com