Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C69549D.2F86A42B@cern.ch> Date: Tue, 12 Feb 2002 18:45:01 +0100 From: "Lassi A. Tuura" Organization: Northeastern University, Boston, USA X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Hildenbrand, Patrick" CC: "'cygwin AT cygwin DOT com'" Subject: Re: cygrunsrv does not start sshd in 1 out of 40 installs References: <1275A224C449D4119CE900508B6FF0B302D32CF2 AT dewdfx20> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > I did follow this discussion, but this one is totally unrelated as the > startup fails every time using cygrunsrv and works ok every time using > invoker AND because sshd even never gets started. sshd never gets started, or never executes? IIRC "service starts" means that it does something magic within 30 seconds of getting executed; otherwise it gets registered as failed to start. That doesn't mean the program didn't run. As for invoker, I do not know what it does -- it could run just enough slower that the other service has a chance to start. You may of course be completely right, the problem could be elsewhere. Just make sure that's the case -- don't dismiss the possibility without trying. I probably can't help you much more as I haven't had this type of service start-up problem, only permission issues that were fairly trivial to solve. Try checking the multitude of permission-related issues people have solved and reported previously on this list. //lat -- Never forget that only dead fish swim with the stream. --Malcolm Muggeridge -- 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/