This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: access port 127.0.0.1:1052 (cygserver question) <PLEASE REPLY TO THIS ONE>
- From: "Conrad Scott" <Conrad dot Scott at dsl dot pipex dot com>
- To: "Robert Collins" <robert dot collins at syncretize dot net>
- Cc: <cygwin-developers at cygwin dot com>
- Date: Thu, 4 Jul 2002 10:44:54 +0100
- Subject: Re: access port 127.0.0.1:1052 (cygserver question) <PLEASE REPLY TO THIS ONE>
- References: <20020704052424.GA15450@redhat.com> <00e601c2232d$a7c5be10$2300a8c0@LAPTOP>
"Robert Collins" <robert.collins@syncretize.net> wrote:
> Sounds like the cygserver domain socket was left open
> (perhaps due to cygserver being forcibly killed),
> and each process was trying to connect to the cygserver.
Rob,
AFAICS it's simply the presence of the socket file (/tmp/cygdaemo)
that triggers this behaviour, i.e. it doesn't require anything to go
wrong to trigger this. You can re-start the machine and the presence
of the file causes clients to attempt to connect to the daemon.
In Un*x, are socket files persistent in this way? Or do they disappear
on last close? I can't see anything unambiguous about this in the
documentation I've got to hand. (I've never programmed with them in
anger and I've no Un*x box to hand to check.) I could go read the
NetBSD or Linux source some more, but I've got other things I'd like
to do this week :-)
As I mentioned in my reply to Chris, cygserver could unlink the socket
file on exit: this isn't what (for example) XEmacs does with its unix
domain sockets, but I don't know of any good reason why cygserver
*shouldn't* do this.
Any thoughts?
// Conrad