From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SE-Linux <selinux@tycho.nsa.gov>
Subject: Re: error: too many arguments to function 'security_getenforce'
Date: Thu, 13 Aug 2009 11:06:10 -0700 [thread overview]
Message-ID: <4A845612.1070907@gmail.com> (raw)
In-Reply-To: <4A844EFD.7030000@redhat.com>
Daniel J Walsh wrote:
>
> Does
>
> selinux_mkload_policy(1);
>
> Work for you?
>
>
I clipped part of the message to keep
things clean.
I'm going to be honest, I'm not that yet skilled
in fixing something like this.
with selinux_mkload_policy(1)
were would I put this?
Justin P. Mattock
--
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:[~2009-08-13 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 3:30 error: too many arguments to function 'security_getenforce' Justin Mattock
2009-08-13 5:49 ` Shintaro Fujiwara
2009-08-13 15:36 ` Justin P. Mattock
2009-08-13 17:35 ` Daniel J Walsh
2009-08-13 18:06 ` Justin P. Mattock [this message]
2009-08-13 18:13 ` Daniel J Walsh
2009-08-13 19:00 ` 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=4A845612.1070907@gmail.com \
--to=justinmattock@gmail.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.