Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<004e01c22338$82f9b9a0$6132bc3e@BABEL>
From:	"Conrad Scott" <Conrad DOT Scott AT dsl DOT pipex DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<Pine DOT LNX DOT 4 DOT 21 DOT 0207040054240 DOT 27963-100000 AT localhost DOT localdomain>
Subject:	Re: access port 127.0.0.1:1052
Date:	Thu, 4 Jul 2002 09:55:12 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000

"Alex Chan" <alexchan AT amazingmedia DOT com> wrote:
> I used strace on some of the commands which were causing
> port 1052 to be accessed and noticed the socket
> /tmp/cygdaemo being opened in each case.
>
> "cat /tmp/cygdaemo" showed:
>
> !<socket >1052 3A1B9DA0-BC44411F-44B9E117-1AA41C07
>
> (note the 1052)
>
> after "rm /tmp/cygdaemo" the behavior went away.
> (I hope it wasn't important.)
>
> Thanks everyone for your help in figuring this one out!

This is the Unix domain socket that the (new) cygserver uses on win
9x/Me systems.  It shouldn't get created unless you run cygserver
itself. but having once run it the socket is left lying around in the
current implementation until you manually remove it.  One side-effect
of not removing it is that every program you run will try to connect
to the (probably non-existent) daemon process and thus you'll get a
second or so delay per process.

A few points:

*) Why is this socket being created?  Can people who saw this
behaviour confirm that they did / didn't run cygserver explicitly?

*) If you're not using cygserver (and you probably aren't), find and
eliminate the /tmp/cygdaemo file if you're running on win9x/Me.

*) The interaction with ZoneAlarm (and probably other such firewalls)
is an utter PITA. If anyone can provide some hints on a setup for any
of these firewalls to shut them up, I would be grateful. Otherwise,
running cygserver (as and when it becomes fully available) will be
very tiresome on win9x/Me systems.

*) This is only a win9x/Me issue: the daemon uses (win32) named pipes
on NT systems.

I hope this helps and my apologies to the confusion this has caused.

// Conrad




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -