Mail Archives: cygwin-developers/2002/07/04/05:25:12

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Message-ID: <00b801c2233c$f67778f0$6132bc3e@BABEL>
From: "Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To: <cygwin-developers AT cygwin DOT com>
References: <20020704052424 DOT GA15450 AT redhat DOT com>
Subject: Re: access port (cygserver question) <PLEASE REPLY TO THIS ONE>
Date: Thu, 4 Jul 2002 10:27:05 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000


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


// Conrad

- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019