All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Martin <antoine@nagafix.co.uk>
To: SELinux <selinux@tycho.nsa.gov>
Cc: wsalamon@tislabs.com, dwalsh@redhat.com
Subject: Re: run_init: Fork:: No such file or directory
Date: Sat, 22 Oct 2005 14:13:01 +0100	[thread overview]
Message-ID: <1129986782.31615.37.camel@localhost.localdomain> (raw)
In-Reply-To: <1129985971.31615.31.camel@localhost.localdomain>

Next time, I'll wait before posting...
I can't explain why that fixed it, but I rebooted, relabeled and now
everything works ok. I've had issues with ttys/ptys before, I guess this
is what has happened here.
Not understanding the problem or the fix makes me nervous though.

Thanks
Antoine



On Sat, 2005-10-22 at 13:59 +0100, Antoine Martin wrote:
> Hi,
> 
> I've been running a system with SELinux enforcing mode for some time
> (Gentoo x86), but since yesterday I can't seem to use run_init to start
> daemons, it fails with:
> Fork:: No such file or directory
> 
> When I straced it, I found that it is failing to open /dev/ptmx|pty?? :
> open("/dev/ptmx", O_RDWR)               = -1 EIO (Input/output error)
> open("/dev/ptyp0", O_RDWR)              = -1 ENXIO (No such device or
> address)
> open("/dev/ptyp1", O_RDWR)              = -1 ENXIO (No such device or
> address)
> (...)
> open("/dev/ptyef", O_RDWR)              = -1 ENXIO (No such device or
> address)
> dup(2)                                  = 3
> fcntl64(3, F_GETFL)                     = 0x2 (flags O_RDWR)
> brk(0)                                  = 0x804b000
> brk(0x806c000)                          = 0x806c000
> fstat64(3, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
> mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
> 0) = 0xb7f17000
> _llseek(3, 0, 0xbfc256e4, SEEK_CUR)     = -1 ESPIPE (Illegal seek)
> write(3, "Fork:: No such file or directory"..., 33Fork:: No such file or
> directory
> ) = 33
> close(3)                                = 0
> munmap(0xb7f17000, 4096)                = 0
> exit_group(71)                          = ?
> 
> Obviously, the devices are there and I'm not using devfs (kernel
> 2.6.13.4) /dev is static on ext3 /.
> I am really stumped. I've tried rebuilding it, rebuilding the libraries
> it depends on, switched to non-enforcing mode, etc.. No luck
> Any ideas would be much appreciated.
> 
> Thanks
> Antoine
> 
> 
> 
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-10-22 13:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-22 12:59 run_init: Fork:: No such file or directory Antoine Martin
2005-10-22 13:13 ` Antoine Martin [this message]
2005-10-22 14:46   ` Petre Rodan
2005-10-22 14:55 ` Chris PeBenito
2005-10-22 15:47   ` Antoine Martin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1129986782.31615.37.camel@localhost.localdomain \
    --to=antoine@nagafix.co.uk \
    --cc=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=wsalamon@tislabs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.