Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3C6A72AA.14EB32AF@cern.ch> Date: Wed, 13 Feb 2002 15:05:30 +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@cygwin.com'" Subject: Re: cygrunsrv does not start sshd in 1 out of 40 installs References: <1275A224C449D4119CE900508B6FF0B302D32CF8@dewdfx20> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > Now anybody some hints on what might happen there ? Anything I could try to > nail down the problem ? Try running cygrunsrv under strace (as the service). I did this once by hacking around the registry, it wasn't too hard, though I don't remember exactly what I did. Remember that strace takes as arguments windows paths and doesn't say much if it fails to execute the program. And that you'll want the output to go to a file. Go to HKLM\SYSTEM\CurrentControlSet\Services\sshd - Change ImagePath to full (windows) path to strace.exe - Change Parameters\AppPath to and Parameters\AppArgs appropriately (I don't remember what I did to separate the args for cygrunsrv from those to sshd, if anything) Usual caveats apply -- hacking around the registry may lobotomise the system. //lat -- Real programmers don't document. Documentation is for simps who can't read the listings or the object deck. -- 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/