From: Ivan Gyurdiev <ivg2@cornell.edu>
To: selinux@tycho.nsa.gov
Cc: Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEMANAGE ] Resync to sepol changes
Date: Mon, 24 Oct 2005 11:10:57 -0400 [thread overview]
Message-ID: <435CF981.7040700@cornell.edu> (raw)
In-Reply-To: <435A8AE9.3020709@cornell.edu>
>
> - change Stub status code of all print functions from STATUS_ERR to
> STATUS_NODATA, so that the flat file parser will exit and not get
> stuck in infinite loop recalling the stubs.
s/print/parse/ here
My file parser loop hands all control over record parsing to the parse()
function, so it is dependent on it to tell it when the last record is
parsed (by signaling STATUS_NODATA), so that's the loop I got rid of for
stubs.
--
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.
prev parent reply other threads:[~2005-10-24 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 18:54 [ SEMANAGE ] Resync to sepol changes Ivan Gyurdiev
2005-10-22 20:03 ` lyris test Remmolt Zwartsenberg
2005-10-22 21:38 ` [ SEMANAGE ] Resync to sepol changes Ivan Gyurdiev
2005-10-24 15:10 ` Ivan Gyurdiev [this message]
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=435CF981.7040700@cornell.edu \
--to=ivg2@cornell.edu \
--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.