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
Date:	Thu, 4 Jul 2002 03:19:12 -0400 (EDT)
From:	Alex Chan <alexchan AT amazingmedia DOT com>
X-Sender:	alexchan AT localhost DOT localdomain
To:	cygwin AT cygwin DOT com
Subject:	Re: access port 127.0.0.1:1052 (cygserver)
In-Reply-To:	<Pine.LNX.4.21.0207040054240.27963-100000@localhost.localdomain>
Message-ID:	<Pine.LNX.4.21.0207040303250.27963-100000@localhost.localdomain>
Flavor:	cheese
MIME-Version:	1.0

Sorry to respond to my own post, but looking at source I realized that
/tmp/cygdaemo is created by cygserver (which I had run earlier as
"cygserver --help" to see what it was all about).

The port 1052 doesn't appear to be that significant.  Running it again it
bound to a different port.  Killing it results in the dangling socket
which is accessed by pretty much every command to see if cygserver is
running/listening.

Busy reading up on cygserver now.  There are several threads in cygwin and
cygwin-developers on this new feature.

-alex


On Thu, 4 Jul 2002, Alex Chan 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.) 
> 


--
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 -