From: Justin Smith <jsmith@mcs.drexel.edu>
To: SELinux@tycho.nsa.gov
Subject: Shutdown issues
Date: 24 Jan 2002 09:02:07 -0500 [thread overview]
Message-ID: <1011880927.1377.9.camel@jsmith.org> (raw)
I am using Redhat 7.2 with the current version of SELinux (2.4.17
kernel) and have noticed some "issues" (sorry to introduce Microsoftese)
involving shutdown:
There are a number of access denied messages in shutdown that are hard
to catch because they don't appear on the message log (since the system
is shutting down).
In some cases, software (postgres and ipchains, for instance) is not
properly shut down due to these denials.
I don't know whether this is related, but I get a kernel panic when
shutting down in enforcing mode. It's hard to note the details of this
problem because the system succeeds in shutting down anyway (so the
messages disappear from the screen). I just recall the phrase 'kernel
panic' appearing briefly. This is only a problem for my home computer
since it shut it down after every use.
In general, I solve all of these problems by using a shutdown script
that puts the system in permissive mode just before shutdown (this is
not a security problem since it's hard to hack a system that is shutting
down...)
--
--
You have received this message because you are subscribed to the selinux 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:[~2002-01-24 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 14:02 Justin Smith [this message]
2002-01-24 15:14 ` Shutdown issues Shaun Savage
2002-01-24 15:37 ` Stephen Smalley
2002-01-24 15:53 ` Stephen Smalley
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=1011880927.1377.9.camel@jsmith.org \
--to=jsmith@mcs.drexel.edu \
--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.