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: Thu, 21 Apr 2005 17:25:01 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Syslogd hangs on start Message-ID: <20050421212501.GB7302@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <41F176E17C92BD46B877AAB6E4C1407B0849FE@XCGCAV06.northgrum.com> <42681963.735FC793@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42681963.735FC793@dessent.net> User-Agent: Mutt/1.5.8i On Thu, Apr 21, 2005 at 02:21:39PM -0700, Brian Dessent wrote: >"Thompson, Lloyd D. (SSD)" wrote: > >> $ net stop syslogd >> The service could not be controlled in its present state. >> >> More help is available by typing NET HELPMSG 2189. >> >> $ net helpmsg 2189 >> >> The service could not be controlled in its present state. > >I do not know the root cause for why the service will not start, but >when it gets in this "hung" state you can unwedge it by killing the >cygrunsrv process. This can get a little tricky because as a SYSTEM >account, it normally can't be killed with taskmgr. I just use Process >Explorer which lets you kill any process, service or not. Find the >cygrunsrv that corresponds with the stuck service (if you have more than >one, click on each and go to the "Services" tab to see which one is for >which service) and kill the stuck one. Then windows should report the >service as stopped and you can try restarting it again after working on >the root cause. Wouldn't "ps -W" and "/bin/kill -f" work here, too? cgf -- 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/