From: Steve Lawrence <slawrence@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>, SELinux <selinux@tycho.nsa.gov>
Subject: Re: Currently we can end up with different permissions on the compiled file_context regex files than the original.
Date: Mon, 25 Aug 2014 13:12:32 -0400 [thread overview]
Message-ID: <53FB6E80.6060700@tresys.com> (raw)
In-Reply-To: <53F4B02C.90701@redhat.com>
> + if (stat(path, &buf) < 0) {
> + fprintf(stderr, "Can not stat: %s: %m\n", argv[0]);
Should the fprintf print path instead of argv[0]?
> + exit(EXIT_FAILURE);
> + }
> +
Looks good otherwise. I'll add to the repo with that change if that's okay.
- Steve
next prev parent reply other threads:[~2014-08-25 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 14:26 Currently we can end up with different permissions on the compiled file_context regex files than the original Daniel J Walsh
2014-08-25 17:12 ` Steve Lawrence [this message]
2014-08-26 11:05 ` Daniel J Walsh
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=53FB6E80.6060700@tresys.com \
--to=slawrence@tresys.com \
--cc=dwalsh@redhat.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.