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 From: "Winston Gutkowski" To: "Ghosty" Cc: "Cygwin" Subject: RE: question about inetd Date: Sun, 19 May 2002 21:41:16 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-Reply-To: Importance: Normal Dunno, but on regular linux I'm pretty sure inetd daemons output via syslogd. You could also try /var/log/... Winston PS: Or even /vap/spool/.../ -----Original Message----- From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf Of Ghosty Sent: Sunday, May 19, 2002 12:10 To: cygwin AT cygwin DOT com Subject: question about inetd I am not sure if this is the right place to ask this question. If not please tell me where I should ask this question. I am using WindozeXP, and I have install inetd as a service for Windoze. Now I have my telnetd running fine. Is it possible to generate a log file that telling me somthing like when, where and error log for the user tries to connect to my telnetd? I have look through man page for inetd and telnetd, I don't see any topic to that. It would be nice if anyone can tell me where I can find information on how to do it. Even better, if you can give me instruction on how to do it also. -- Ghosty "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners" - Ernst Jan Plugge -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/