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 Date: Mon, 24 Feb 2003 16:52:44 -0500 From: Jason Tishler Subject: Re: exim 4.12-3 winsock problem (was Re: 1.3.21) In-reply-to: <3E5A8939.CE055B7F@ieee.org> To: cygwin@cygwin.com Mail-followup-to: cygwin@cygwin.com Message-id: <20030224215244.GA2612@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20030221153741.GA26756@redhat.com> <20030221180822.GB1408@tishler.net> <3E566E49.53BE7CBE@ieee.org> <20030221191209.GE1408@tishler.net> <20030224200201.GA2348@tishler.net> <3E5A8939.CE055B7F@ieee.org> Pierre, On Mon, Feb 24, 2003 at 04:06:01PM -0500, Pierre A. Humblet wrote: > If you run with -d you will see that exim sheds all supplementary > groups. I was just following the README: cygrunsrv -I exim -p /usr/bin/exim -e CYGWIN=ntsec \ -a "-bdf -q15m" -d "Exim Mail Transfer Agent" \ -1 /var/log/exim/cygrunsrv_out.log -2 /var/log/exim/cygrunsrv_err.log Should I no longer use the "-d" option? > As a first step you should make sure that the primary group of SYSTEM > is 544 on your system and not 18 (as it used to be 6 months back). > That's needed to setuid, but I am not exactly sure how it relates to > wsock. I tried the above is still no luck: $ id uid=18(SYSTEM) gid=544(Administrators) groups=544(Administrators) $ ~jt/src/exim-4.12-3/build-CYGWIN-i386/exim -bdf -q15m 2003-02-24 16:35:38 cannot find smtp/tcp service when starting daemon > Can you better explain your setup, i.e. what user are you running exim > under normally, when you debug, when you strace, etc.... I run all of the above under the LocalSystem account. > > $ exim -bdf -q15m > > wsock_init(): wsock_started = 0 > > wsock_init(): wsastartup = 0x7503d2c3 > > wsock_init(): wsastartup() returned 10107 > > getservbyname() failed with last error = 10093 > > Don't you think that failing to start wsock deserves a system_printf? Are you asking me specifically? Or, is this a rhetorical question for other Cygwin developers too? Given my experience trying to debug this problem, I guess that I would vote "yes". Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/