From: Joshua Brindle <method@gentoo.org>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest policycoreutils patch
Date: Fri, 08 Sep 2006 10:33:53 -0400 [thread overview]
Message-ID: <45017F51.80200@gentoo.org> (raw)
In-Reply-To: <45001F1A.3080004@redhat.com>
Daniel J Walsh wrote:
> For some reason this did not go out last week.
>
> More translations.
>
> Change all python to use /usr/bin/python -E, to make it a little bit
> harder to muck with.
>
> Have newrole ignore sigpipe so it gives correct error message when
> flooded with 4000 character security context.
>
> Add -i qualifier to restorecon to tell it to ignore files that do not
> exist. This fixes a problem in
> fixfiles -R rpmlint restore
>
I'm not sure about this. Most other commands don't have a feature like
this (if they do its generally -f anyway, like rm -f ) and it seems like
fixfiles should be interpreting the error correctly instead of ripping
the error passing out of restorecon.
> Which could hand restorecon files that do not exists and restorecon
> prints ugly warnings.
>
why not a -q then? I think it should still return a proper error code
but it doesn't have to spam the console
> restorecond init script description needs line continuation marks to
> make system-config-services happy.
>
--
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:[~2006-09-08 14:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 13:31 Latest policycoreutils patch Daniel J Walsh
2006-09-08 14:00 ` Karl MacMillan
2006-09-08 14:33 ` Joshua Brindle [this message]
2006-09-08 14:55 ` Karl MacMillan
2006-09-08 14:35 ` Stephen Smalley
2006-09-08 16:37 ` Daniel J Walsh
2006-09-08 20:25 ` Stephen Smalley
2006-09-11 12:25 ` Joshua Brindle
2006-09-12 12:45 ` Karl MacMillan
2006-09-13 15:14 ` Joshua Brindle
-- strict thread matches above, loose matches on Subject: below --
2006-11-06 15:25 Daniel J Walsh
2006-01-17 20:34 Daniel J Walsh
2006-01-18 1:36 ` Joshua Brindle
2006-01-18 1:37 ` Joshua Brindle
2006-01-18 3:40 ` Daniel J Walsh
2006-01-18 3:41 ` Joshua Brindle
2006-01-18 3:48 ` Daniel J Walsh
2006-01-18 3:51 ` Joshua Brindle
2006-01-18 7:02 ` Ivan Gyurdiev
2006-01-18 15:44 ` Daniel J Walsh
2006-01-18 18:00 ` Ivan Gyurdiev
2006-01-18 18:12 ` Ivan Gyurdiev
2006-01-18 18:30 ` Stephen Smalley
2006-01-18 18:36 ` Ivan Gyurdiev
2006-01-18 18:52 ` Stephen Smalley
2006-01-18 19:04 ` Ivan Gyurdiev
2006-01-18 19:32 ` Stephen Smalley
2006-01-18 19:07 ` Daniel J Walsh
2006-01-18 19:15 ` Ivan Gyurdiev
2006-01-18 19:19 ` Daniel J Walsh
2006-01-18 19:59 ` Stephen Smalley
2006-01-18 20:01 ` Ivan Gyurdiev
2006-01-19 14:27 ` Daniel J Walsh
2006-01-18 16:13 ` Stephen Smalley
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=45017F51.80200@gentoo.org \
--to=method@gentoo.org \
--cc=dwalsh@redhat.com \
--cc=sds@tycho.nsa.gov \
--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.