From: Tom <tom@lemuria.org>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: run_init woes
Date: Thu, 22 May 2003 11:28:39 +0200 [thread overview]
Message-ID: <20030522112833.A2615@lemuria.org> (raw)
I've started writing a policy for PXE daemon, improving tftpd policy,
etc - when something weird happend to me.
# run_init /etc/init.d/pxe start
Authenticating root.
Password:
Starting PXE daemon: Intel PXE daemon, PXE-2.0 Beta-1 (build 001)
Copyright (C) 1999 Intel Corporation
pxe.
So far, so good. Except that the pxe daemon dies right away. No debug
output either, nothing in the logfiles.
However, if I do
# /etc/init.d/pxe start
Everything works just fine. (the machine is running in permissive mode)
Except that it runs in the wrong domain, of course. But IMHO this shows
that the problem isn't in the pxe daemon.
Also, if I do a reboot, the pxe daemon comes up just fine, running in
the correct domain and everything.
Is there anything in run_init that could cause this kind of problems?
If so, what can I about it? If not, what is it that I'm missing here?
(I have the feeling I've had this before, but I could find nothing in
the mailing list archive)
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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.
next reply other threads:[~2003-05-22 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 9:28 Tom [this message]
2003-05-22 12:10 ` run_init woes Stephen Smalley
2003-05-22 13:32 ` Tom
2003-05-22 12:41 ` Russell Coker
2003-05-22 13:39 ` Tom
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=20030522112833.A2615@lemuria.org \
--to=tom@lemuria.org \
--cc=selinux@tycho.nsa.gov \
/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.