Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <5.2.0.9.2.20030218175443.02b4f888@pop3.cris.com> X-Sender: rrschulz@pop3.cris.com Date: Tue, 18 Feb 2003 17:56:55 -0800 To: cygwin@cygwin.com From: Randall R Schulz Subject: Re: error setting up ipc-daemon In-Reply-To: <3E52D900.9030708@ece.gatech.edu> References: <5.2.0.9.2.20030218100657.01da6858@pop3.cris.com> <5.2.0.9.2.20030218080515.02ee9710@pop3.cris.com> <5.2.0.9.2.20030218100657.01da6858@pop3.cris.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Charles, I mentioned inetd because the similarity of symptoms I experienced to those that befell Daku. Randall Schulz At 17:08 2003-02-18, Charles Wilson wrote: >Randall R Schulz wrote: >>Igor, >>I was under the impression that the currently recommend way to get >>inetd running as a cygwin service was this: >> inetd --install-as-service >>The resulting Windows service does not use cygrunsrv to invoke >>inetd--it is launched directly: >>Path to executable: D:\cygwin\usr\sbin\inetd.exe > > >Umm, fellas? This isn't about inetd. It's about ipc-daemon... > >fortunately, ipc-daemon and inetd are a lot alike; neither uses cygserver. > >--Chuck -- 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/