All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Seth D. Guikema" <sguikema@jhu.edu>
To: selinux@tycho.nsa.gov
Subject: reindexing time for SELinux?
Date: Mon, 04 Feb 2008 09:21:45 -0500	[thread overview]
Message-ID: <47A71F79.1020300@jhu.edu> (raw)

I am trying to set up SELinux on my Fedora Core 7 workstation. I am 
using the pre-installed GUI SELinux configuration tool in FC7. I 
selected a targeted set-up. I was warned that the workstation would need 
to reindex the files at the next reboot and that this would take a 
while. I clicked ok. I rebooted the workstation Saturday morning at 
about 10am. It is still unresponsive (and not available for remote 
connections) and working hard this morning, almost 48 hours later. How 
long should reindexing take? The workstation is new. It has 2 1TB disks 
(RAID mirrored), but there isn't much on them yet - perhaps 30MB plus 
the OS and other programs installed by the manufacturer (ASL). Does 
reindexing really take this long? This is my first attempt at SELinux, 
and any help is appreciated. Thank you.

Sincerely,
Seth Guikema

-- 
Assistant Professor
Department of Geography and Environmental Engineering
Johns Hopkins University
Baltimore, MD 21218
(410)516-6042
sguikema@jhu.edu
https://jshare.johnshopkins.edu/sguikem1/public_html/


--
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:[~2008-02-04 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 14:21 Seth D. Guikema [this message]
2008-02-04 15:09 ` reindexing time for SELinux? Stephen Smalley
2008-02-04 19:03   ` Seth D. Guikema
2008-02-04 15:52 ` Daniel J Walsh
2008-02-04 19:16 ` Russell Coker

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=47A71F79.1020300@jhu.edu \
    --to=sguikema@jhu.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.