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: Mon, 30 Aug 2004 10:29:24 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Marcin Lewandowski cc: cygwin AT cygwin DOT com Subject: Re: cygrunsrv xinetd problem In-Reply-To: <000b01c48e7a$732056b0$3601010a@plas> Message-ID: References: <001501c48db4$059224f0$3601010a AT plas> <002801c48dd2$8a76b320$3601010a AT plas> <004101c48e09$eab88e70$3601010a AT plas> <000b01c48e7a$732056b0$3601010a AT plas> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Mon, 30 Aug 2004, Marcin Lewandowski wrote: > > > Well, still doesn't work. That's what I did: > > > First, I checked normal windows permissions - SYSTEM has all rights > > > to c:\cygwin dir and subdirs, inherited from permissions to whole drive. > > > Next, I checked 'linux' permissions displayed by 'ls -al', and changed > > > them to 755, since user 'Marcin' owns both files. > > > > Did you also check the permissions on all the programs that xinetd tries > > to invoke (e.g., /usr/sbin/ftpd.exe, if you enabled ftp)? > > OK, I've changed many things since yesterday, so I'll write what I've done: > First of all, I removed cygwin completely from the disk and the registry, > and reinstalled it as Administrator (previously I installed it as user > Marcin). > Next, I made passwd and group files, and changed all dirs/subdirs/files to > be owned by Adminitrator, group Users. Sounds radical, but whatever works. :-) > Then I tried to run sshd service, so firstly (as Administrator) I run > $ ssh-host-config > and typed some yes'es. Then, I type: > $ cygrunsrv -S sshd > and guess what - error 1062. After some tries, I looked at > /var/log/sshd.log, > and found: > Could not load host key: /etc/ssh_host_key > Could not load host key: /etc/ssh_host_rsa_key > Could not load host key: /etc/ssh_host_dsa_key > Disabling protocol version 1. Could not load host key > Disabling protocol version 2. Could not load host key > sshd: no hostkeys available -- exiting. > So, I chmod'ed those files to 755 and everything went good from this point. You're actually better off chown'ing these to SYSTEM:Administrators... > Then, I tried running: > $ cygrunsrv -S xinetd > but, the same story, error 1062. So, as you suggested, i made: > $ chmod a+rx * > in directories /bin and /usr/sbin. That didn't help, but now when I look at > /var/log/xinetd.log, I don't see nothing, but a couple of lines: > xinetd: msg_init failed: can't open log file Aha. > I can't see a problem with this from this point, here's the listing of > /var/log: > total 1477 > drwxrwx---+ 4 Administ Users 0 Aug 30 12:02 . ^ Here's your culprit. You need a +x permission on the directory to be able to see files in that directory. A "chmod o+x /var/log" should fix this. In fact, make sure every directory other than the user home directories is executable by others. > drwxr-xr-x+ 13 Administ Users 0 Aug 30 10:53 .. > drwxrwx---+ 2 Administ Users 0 Aug 30 00:01 apache > drwxrwx---+ 2 Administ Users 0 Aug 30 00:07 exim > -rw-r--r-- 1 Marcin None 0 Aug 30 12:02 ls.log > -rwxr-x---+ 1 Administ Users 103442 Aug 30 10:41 setup.log > -rwxr-x---+ 1 Administ Users 1400010 Aug 30 10:41 setup.log.full > -rw-r--r-- 1 SYSTEM root 2328 Aug 30 11:11 sshd.log > -rw-rw-rw- 1 Administ Users 2156 Aug 30 11:15 wtmp > -rw-r--r-- 1 SYSTEM root 225 Aug 30 12:01 xinetd.log > > > Try opening a SYSTEM-owned shell (see the recent thread, > > ), and run xinetd > > directly from the command line in that shell. If it runs there, compare > > the environment settings for the service with the environment settings in > > that shell. If it doesn't run there, the errors you get should be helpful > > in diagnosing the problem and experimenting. > > Well, looks like xinetd runs well when running as SYSTEM directly, under > SYSTEM owned shell. No errors, and I was even able to login using telnet > service. So, I guess the problem is not here. Yes, the log file problem wouldn't show up in the SYSTEM-owned shell, unless you also tried to redirect std{out,err} to /var/log/xinetd.log (i.e., run "/usr/sbin/xinetd >>/var/log/xinetd.log 2>&1", which is essentially what cygrunsrv does). 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/