delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/11/25/12:17:07

X-Spam-Check-By: sourceware.org
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: /dev/console : permission denied
Date: Fri, 25 Nov 2005 17:16:56 -0000
MIME-Version: 1.0
In-Reply-To: <20051125164659.GE8670@trixie.casa.cgf.cx>
Message-ID: <SERRANO7T9R4OjCqUsR0000017f@SERRANO.CAM.ARTIMI.COM>
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
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

Christopher Faylor wrote:
> On Fri, Nov 25, 2005 at 02:24:53PM -0000, Dave Korn wrote:
>> Christopher McIntosh wrote:
>>> Consequently, I am back to the issue which I was first
>>> reporting/investigating: Why does init report open(/dev/console) :
>>> permission denied.
>> 
>> strace might be able to tell you that.
>> 
>>> SUMMARY: 1.  'cygcheck -s -v -r' causes an error when executed within a
>>> Cygwin shell (bash, sh, etc.); but is successful when executed within a
>>> CMD shell.
>> 
>> Did you try removing 'tty' from $CYGWIN yet?
> 
> I don't know about the cygcheck error but the /dev/console problem
> sounds like cygwin working as designed.  From the description, it
> sounds like expected behavior to me.  Something is trying open
> "/dev/console" when there is no console and is getting an error.
> 
> Well, duh.
> 
> cgf


  Oh, you can't open it when there's not one bound?  Fair enough.  

  Must be syslogd then.  Chris M, did you run the syslogd-config script or
install it manually?

Service             : syslogd
Display name        : CYGWIN syslogd
Current State       : Running
Controls Accepted   : Stop
Command             : /usr/sbin/syslogd -D
stdin path          : /dev/null
stdout path         : /var/log/syslogd.log
stderr path         : /var/log/syslogd.log
Process Type        : Own Process
Startup             : Automatic
Account             : LocalSystem

  Hmm, looks right though.  (Interestingly enough both the config script and
the cygwin-specific readme refer to an apparantly-bogus "-a" flag.  I'm on
1.3.2-29.)  Perhaps it's one of the destinations in syslog.conf that is the
source of the problem then.  What's your syslog.conf look like?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019