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 Message-ID: <001d01c48ea9$e860ed20$3601010a@plas> From: "Marcin Lewandowski" To: References: <001501c48db4$059224f0$3601010a AT plas> <002801c48dd2$8a76b320$3601010a AT plas> <004101c48e09$eab88e70$3601010a AT plas> <000b01c48e7a$732056b0$3601010a AT plas> Subject: Re: cygrunsrv xinetd problem Date: Mon, 30 Aug 2004 17:56:26 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes > > 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. Done, and still the same error... > > > 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). I tried doing this, and xinetd runs with no problems. Marcin Lewandowski http://www.ii.uj.edu.pl/~lewandow -- 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/