All of lore.kernel.org
 help / color / mirror / Atom feed
From: justinmattock@gmail.com (Justin P. Mattock)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] amanda's global requirements were not met: type/attribute inetd_t (No such file or directory).
Date: Sat, 04 Sep 2010 06:38:39 -0700	[thread overview]
Message-ID: <4C824BDF.1050200@gmail.com> (raw)
In-Reply-To: <20100904132452.GA26899@localhost.localdomain>

On 09/04/2010 06:24 AM, Dominick Grift wrote:
> On Sat, Sep 04, 2010 at 06:21:08AM -0700, Justin P. Mattock wrote:
>> On 09/04/2010 01:46 AM, Dominick Grift wrote:
>>> On Fri, Sep 03, 2010 at 08:18:55PM -0700, Justin Mattock wrote:
>>>> Im not sure what I need todo to make amanda happy with this:
>>>> sudo make load
>>>>
>>>>   /usr/share/selinux/mcs/zebra.pp -i /usr/share/selinux/mcs/zosremote.pp
>>>> libsepol.print_missing_requirements: amanda's global requirements were
>>>> not met: type/attribute inetd_t (No such file or directory).
>>>> libsemanage.semanage_link_sandbox: Link packages failed (No such file
>>>> or directory).
>>>> /usr/sbin/semodule:  Failed!
>>>> make: *** [load] Error 1
>>>>
>>>> do I need amanda and sandbox both working for this to work?
>>>
>>> Amanda's global requirements were not met. It has policy to interact with inetd_t but the type is not available:
>>>
>>> 1. is the inetd_t included (made available) in the amanda module?
>>> 2. is the xinetd policy installed?
>>
>> alright... disabling the build of this module, gets me going...
>> as for the xinetd I don't have that on the system, as well as amanda
>
> dependency issue. Ive mentioned issues like this on the IRC channel the other day.
> Refpolicy maintainer does not want to change it.
>
> We need semanage/compiler to tell us in plain language the a dependency was not met and which module(s) solve the dependencies.
>

well to just error out(i think) is not really a good idea(leaves users 
in a panic)..maybe some

#ifdef AMANDA_XINE_STUFF
SELINUX_AMANDA_MODULE_NO_BUILDY
#endif

or even simpler a warning for this, but then again if somebody is 
setting up a policy like this then adjusting the modules should be 
something they do without even thinking about it(for the record I never 
do...)



Justin P. Mattock

  reply	other threads:[~2010-09-04 13:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04  3:18 [refpolicy] amanda's global requirements were not met: type/attribute inetd_t (No such file or directory) Justin Mattock
2010-09-04  8:46 ` Dominick Grift
2010-09-04 13:21   ` Justin P. Mattock
2010-09-04 13:24     ` Dominick Grift
2010-09-04 13:38       ` Justin P. Mattock [this message]
2010-09-04 15:20       ` Chris PeBenito
2010-09-05 15:14         ` Justin P. Mattock

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=4C824BDF.1050200@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=refpolicy@oss.tresys.com \
    /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.