All of lore.kernel.org
 help / color / mirror / Atom feed
From: domg472@gmail.com (Dominick Grift)
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, 4 Sep 2010 10:46:23 +0200	[thread overview]
Message-ID: <20100904084622.GA22243@localhost.localdomain> (raw)
In-Reply-To: <AANLkTimUxiZXh=W9p9+A8Rq=H2G8=yTjh1exQ-onx9iR@mail.gmail.com>

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?

> 
> 
> -- 
> Justin P. Mattock
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20100904/685c486b/attachment.bin 

  reply	other threads:[~2010-09-04  8:46 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 [this message]
2010-09-04 13:21   ` Justin P. Mattock
2010-09-04 13:24     ` Dominick Grift
2010-09-04 13:38       ` Justin P. Mattock
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=20100904084622.GA22243@localhost.localdomain \
    --to=domg472@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.