X-Spam-Check-By: sourceware.org Message-ID: X-Sender: karlm30 AT hotmail DOT com In-Reply-To: From: "Karl M" To: cygwin AT cygwin DOT com Subject: Re: services not starting with 20060104 snapshot Date: Thu, 05 Jan 2006 15:33:57 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Hi Igor... >From: Igor Peshansky Subject: Re: services not starting with 20060104 >snapshot >Date: Thu, 5 Jan 2006 16:34:59 -0500 (EST) > >On Thu, 5 Jan 2006, Karl M wrote: > > > Hi Igor... > > > > > From: Igor Peshansky > > > CC: cygwin AT XXXXXX DOT XXX > >Ahem... > > > > Subject: Re: services not starting with 20060104 snapshot > > > Date: Thu, 5 Jan 2006 15:21:37 -0500 (EST) > > > > > > On Thu, 5 Jan 2006, Karl M wrote: > > > > > > > I tried the latest snapshot cygwin1-200601051745.dll.bz2 on my SP1 > > > > box and I still can't start services; went back to > > > > cygwin1-20060103.dll.bz2. > > > > > > Karl, sorry to belabor the obvious, but have you completely killed the > > > service processes before updating the DLL? For me, after every > > > unsuccessful service startup, there was a stale cygrunsrv process left > > > that could be keeping the old DLL in memory. > > > > Unfortunately, yes...I stopped everything first. And after I copy it in, > > I run a script that resets my mounts all permissions on my cygwin > > install because setup seems to muck that up sometimes. Then I start > > everything back up. > >Again, not to quibble over terminology, but did you actually do a "ps -ef" >and "kill -9" the stale cygrunsrv processes? In my case, when the service >failed to start, stopping it didn't work either (at least as far as the >stale processes were concerned). Just to dot all the i's, look in the >Task Manager for any process that has "cygrunsrv" as its executable name. >HTH, Yes I always do that. 0) open a bash shell window 1) bunzip2 the dll 2) net stop openssh; net stop agent0; ps -ef 3) exit (after looking at the screen) 4) run setup if needed 5) copy the cygwin1.dll to C:\Cygwin\bin 6) open a bash shell window 7) cygwin-host-config; openssh-service-install; net start agent0; ps -ef this last line fixes up the mounts and perms, uninstalls and reinstalls the sshd service (so the path is updated), restarts my ssh-agent, and lets me see that it went ok. I do this as administrator (I'm normally restricted user), so these things stay in my history and so I actually type cd /c/.../Desktop/ !bun !net exit and !cygwin-hos Thanks, ...Karl -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/