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
Date: Sun, 29 Aug 2004 15:14:26 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: cygrunsrv xinetd problem
In-Reply-To: <4132250E.C3006DFD@dessent.net>
Message-ID: <Pine.GSO.4.61.0408291503010.14676@slinky.cs.nyu.edu>
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> <4132250E DOT C3006DFD AT dessent DOT net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Scanned-By: MIMEDefang 2.39

On Sun, 29 Aug 2004, Brian Dessent wrote:

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

Very true.  And you're right that the User's Guide probably should have
some words to that effect.  If one needs to test the service by running
the executable directly, it's probably best to do that from a SYSTEM-owned
shell (see the recent thread: <http://cygwin.com/ml/cygwin/2004-08/msg01132.html>).

> 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

Good point.  Again, this probably belongs in the User's Guide or the FAQ
-- that, and the bit about deleting the log files after testing services
as normal users.
	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/