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