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: Fri, 29 Apr 2005 15:34:49 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: can't access Serial Ports Message-ID: <20050429133449.GB2572@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20050428204626 DOT 29949 DOT qmail AT web54701 DOT mail DOT yahoo DOT com> <427235F5 DOT 8040907 AT byu DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <427235F5.8040907@byu.net> User-Agent: Mutt/1.4.2i On Apr 29 07:26, Eric Blake wrote: > crw--w--w- 1 eblake None 1, 7 Apr 29 06:45 full > srw-rw-rw- 1 SYSTEM root 53 Apr 28 06:08 log= > crw-rw-rw- 1 eblake None 1, 3 Apr 29 06:45 null > > It looks like the relatively new syslogd is responsible for /dev/log. Yes, it creates and destroys this UNIX socket during runtime. Don't touch it. You have been warned. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- 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/