Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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: <4132250E.C3006DFD@dessent.net>
Date: Sun, 29 Aug 2004 11:48:46 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygrunsrv xinetd problem
References: <001501c48db4$059224f0$3601010a AT plas> <Pine DOT GSO DOT 4 DOT 61 DOT 0408290934290 DOT 14676 AT slinky DOT cs DOT nyu DOT edu> <002801c48dd2$8a76b320$3601010a AT plas> <Pine DOT GSO DOT 4 DOT 61 DOT 0408291227350 DOT 14676 AT slinky DOT cs DOT nyu DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Igor Pechtchanski wrote:

> > Nastepujace informacje sa czescia zdarzenia: xinetd : PID 3680 :
> > starting service `xinetd' failed: execv: 1, Operation not permitted."
> 
> This, however, says:
> 
> "The following information is part of the event: xinetd : PID 3680 :
> starting service `xinetd' failed: execv: 1, Operation not permitted."
> 
> Which is the actual message from xinetd, and is *very* helpful.  This
> basically says that the service manager couldn't execute the xinetd
> program when running as SYSTEM.  Check the permissions on both
> /usr/sbin/xinetd and /bin/cygwin1.dll (and whatever other DLLs the xinetd
> program depends on -- see the output of "cygcheck /usr/sbin/xinetd.exe").
> Make sure all of them are executable by SYSTEM.

The OP also mentioned the common line, "but I ran it as a normal user
and it started fine."  There should be a big "NO! don't do this!"
somewhere in the Users Guide about testing a service by running it from
your regular user account.  Doing so can create log, pid, etc. files
with the wrong ownership and permissions, so that when you later run it
as SYSTEM it fails because it cannot write or delete those files.  It's
always helpful to nuke all traces of these kinds of files when trying to
get a service to start that is erroring.

In this particular case it's probably not the problem because the error
would likely be "Permission denied" and not "Operation not permitted",
and so Igor's advise about checking for +x is probably right.  But I
thought I'd mention it as I've seen this bite people many times.

Brian

--
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/