From: Michael C Thompson <thompsmc@us.ibm.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: genhomedircon bug
Date: Sun, 12 Nov 2006 15:26:35 -0600 [thread overview]
Message-ID: <4557918B.20909@us.ibm.com> (raw)
I found a bug in genhomedircon:
policycoreutils.x86_64 1.32-3
# genhomedircon
libsemanage.semanage_direct_connect: could not establish direct connection
libsemanage.assert_init: A direct or server connection is needed to use
this function - please call the corresponding connect() method
libsemanage.enter_ro: could not enter read-only section
Traceback (most recent call last):
File "/usr/sbin/genhomedircon", line 379, in ?
selconf = selinuxConfig(directory, type, usepwd)
File "/usr/sbin/genhomedircon", line 140, in __init__
(status, self.ulist) = semanage_user_list(self.semanageHandle)
TypeError: unpack non-sequence
# id
uid=0(root) gid=0(root)
groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)
context=staff_u:secadm_r:secadm_t:SystemLow-SystemHigh
Thanks,
Mike
--
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:[~2006-11-12 21:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4557918B.20909@us.ibm.com \
--to=thompsmc@us.ibm.com \
--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.