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: <cygwin-developers at cygwin dot com>
- Date: Thu, 4 Jul 2002 10:27:05 +0100
- Subject: Re: access port 127.0.0.1:1052 (cygserver question) <PLEASE REPLY TO THIS ONE>
- References: <20020704052424.GA15450@redhat.com>
Chris,
Sorry for the delay in replying but for once I'd managed to get some
sleep during nightime hours --- it probably won't happen again :-)
I've replied to this on the cygwin mailing list, but just to confirm
that this is an issue only on win9x/Me and only if someone has run
cygserver at least once (to create the /tmp/cygdaemo socket).
The current cygserver implementation leaves the socket file around on
exit, which is standard behaviour for a daemon process AFAIK. I've
been meaning to put in a patch to get it to delete the socket when the
daemon exits: I'll submit it to you for HEAD if you're interested.
But, this only occurs if people have run cygserver themselves: none of
this happens by default.
As for the firewall problem: that is a right PITA: I've got in the
habit of clicking on the ZoneAlarm popup whenever it appears, since it
all settles down after a while but it's a stupid experience. I'll see
if I can find out how to configure it to ignore all local socket
connections.
HTH.
// Conrad