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 19:19:43 -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: <002b01c48ee2$b74741b0$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> <001d01c48ea9$e860ed20$3601010a AT plas> <002b01c48ee2$b74741b0$3601010a AT plas> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Tue, 31 Aug 2004, Marcin Lewandowski wrote: > > > > 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 > > > > > > 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. > > 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). HTH, 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/