From: Sven Vermeulen <sven.vermeulen@siphos.be>
To: selinux@tycho.nsa.gov
Subject: Re: What provides _policy?
Date: Fri, 3 May 2013 19:39:26 +0200 [thread overview]
Message-ID: <20130503173926.GA22935@siphos.be> (raw)
In-Reply-To: <20130501135544.GA21525@siphos.be>
On Wed, May 01, 2013 at 03:55:44PM +0200, Sven Vermeulen wrote:
> Recent policycoreutils' sepolicy imports "_policy", but I am having troubles
> finding where _policy is provided?
Okay so I know that _policy comes from policy.c which is build through
"setup.py build" and is provided through a _policy.so file (I was looking
for _policy.py which isn't created).
However, I'm having a hard time debugging why I get the following:
File "/usr/bin/sepolicy-2.7", line 63, in __call__
from sepolicy.network import domains
File "/usr/lib64/python2.7/site-packages/sepolicy/network.py", line 44, in <module>
portrecs, portrecsbynum = _gen_port_dict()
File "/usr/lib64/python2.7/site-packages/sepolicy/network.py", line 31, in _gen_port_dict
for i in info(sepolicy.PORT):
File "/usr/lib64/python2.7/site-packages/sepolicy/__init__.py", line 182, in info
dict_list = _policy.info(setype, name)
RuntimeError: No such file or directory
What could this error be about? I get this when I try
"sepolicy communicate -s portage_t".
Wkr,
Sven Vermeulen
--
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 prev parent reply other threads:[~2013-05-03 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 13:55 What provides _policy? Sven Vermeulen
2013-05-03 17:39 ` Sven Vermeulen [this message]
2013-05-06 16:52 ` Daniel J Walsh
2013-05-06 18:38 ` Sven Vermeulen
2013-05-06 18:52 ` Daniel J Walsh
2013-05-07 8:33 ` Sven Vermeulen
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=20130503173926.GA22935@siphos.be \
--to=sven.vermeulen@siphos.be \
--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.