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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 12 Sep 2004 11:36:42 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: cygwin AT cygwin DOT com Subject: Re: cygserver service won't start In-Reply-To: <20040912144634.GE17670@cygbert.vinschen.de> Message-ID: References: <20040909080829 DOT GC2953 AT cygbert DOT vinschen DOT de> <20040910080758 DOT GE468 AT cygbert DOT vinschen DOT de> <20040911123916 DOT GA8906 AT cygbert DOT vinschen DOT de> <20040912144634 DOT GE17670 AT cygbert DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Sun, 12 Sep 2004, Corinna Vinschen wrote: > On Sep 11 13:06, Igor Pechtchanski wrote: > > On Sat, 11 Sep 2004, Alder wrote: > > > On a perfect platform, perhaps, but like I said, I really had to add > > > it because without it there a Windows dialog would pop up when I ran > > > cygserver telling me that 'Cygwin1.dll' could not be found. That > > > was also true on my previous installation, and one of the reasons I > > > thought it best to reinstall. > > This is weird. I never observed that and I installed a lot of services > using cygrunsrv on a good number of machines. > > > I'm observing similar behavior, but it looks like our causes may be > > different. > > Igor, out with your debugging experiences! I believe they, along with a description of the fix, are summarized in , which seems to have been overlooked, as it never got any reply (the rest of the thread deteriorated into a discussion of the need for check_case:strict). I'd like to get some feedback on whether my analysis and the fix plan are correct, before I go through the machinery of getting the patch approved. > > If your cygcheck showed that you have check_case:strict in your CYGWIN > > variable, I'd've guessed that this is another instance of the bug I > > reported on the cygwin-developers list (where the PATH got truncated on > > converting it back to Win32 format). The fact that cygrunsrv *appends* > > /bin to the PATH, whereas you *prepend* it, seems to argue strongly for > > this. > > > > Just for the sake of completeness, though, could you please try adding a > > service that basically invokes cmd.exe with '-c "echo %PATH%"' as > > arguments, and see what the PATH is in the log after starting the service? > > Yes, I would be curios as well. FWIW, I ended up using the following for sshd as a workaround: cygrunsrv -I sshd -d "CYGWIN sshd" -p /usr/sbin/sshd -a "-De" -1 /var/log/sshd.log -2 /var/log/sshd.log -e "CYGWIN=check_case:strict ntsec notitle binmode nosmbntsec notty" -e "PATH=/usr/bin:/bin" -t manual -o ^^^^^^^^^^^^^^^^^^^^^^^ Incidentally, -1 and -2 didn't work for me with optional arguments (if I simply said "-1 -2", stdout was redirected to a file called "-2"). I'm sure it's unrelated, but thought I'd mention it. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Happiness lies in being privileged to work hard for long hours in doing whatever you think is worth doing." -- Dr. Jubal Harshaw -- 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/