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: <000701c48f30$794d5590$3601010a@plas>
From: "Marcin Lewandowski" <lewandom AT op DOT pl>
To: <cygwin AT cygwin DOT com>
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> <004101c48e09$eab88e70$3601010a AT plas> <Pine DOT GSO DOT 4 DOT 61 DOT 0408291707520 DOT 17405 AT slinky DOT cs DOT nyu DOT edu> <000b01c48e7a$732056b0$3601010a AT plas> <Pine DOT GSO DOT 4 DOT 61 DOT 0408301025020 DOT 24572 AT slinky DOT cs DOT nyu DOT edu> <001d01c48ea9$e860ed20$3601010a AT plas> <002b01c48ee2$b74741b0$3601010a AT plas> <Pine DOT GSO DOT 4 DOT 61 DOT 0408301916210 DOT 23400 AT slinky DOT cs DOT nyu DOT edu>
Subject: Re: cygrunsrv xinetd problem
Date: 	Tue, 31 Aug 2004 09:59:39 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

> > The thing is, I suppose, that it's not the fault of cygrunsrv's logging.
> > It's a problem with xinetd internal logging, according to sources made
by
> > some kind of utility 'xlog' (I haven't heard about it). Precisely, I
think,
> > that the error is raised by function 'msg_init' in file 'msg.c',
somewhere
> > here (i use code cutting):
> >
> > type_of_xlog = XLOG_FILELOG ;
> > xh = xlog_create( type_of_xlog, program_name,
> >              XLOG_PRINT_ID + XLOG_PRINT_PID,
> >              filelog_option_arg, LOG_OPEN_FLAGS, LOG_FILE_MODE ) ;
> > if ( xh == NULL )
> >   if ( type_of_xlog == XLOG_FILELOG )
> >     return( "can't open log file" ) ;
> >
> > As, i don't have 'xlog' sources, I don't know what is the exact path of
> > the trouble-making log file. However, I suspect that it might be a
problem
> > of doubling the logfile: cygrunsrv opens /var/log/xinetd.log to write
his
> > messages, and next xinetd tries to open the same file for his logging.
> >
> > How do you think, is it possible, and if so, what should I do to
overcome
> > the problem?
>
> Well, if you really think it's a clash between cygrunsrv's log and
> xinetd's one, you can instruct cygrunsrv to use a different log name using
> the "-1" and "-2" cygrunsrv arguments (see "cygrunsrv --help" for
> details).

Yes, this helps, after these three lines:
$ cygrunsrv -R xinetd
$ cygrunsrv -I xinetd -p /usr/sbin/xinetd -d 'CYGWIN xinetd' -1 /dev/null -2
/dev/null
$ cygrunsrv -S xinetd
xinetd service runs just well.

Thanks for help

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/