From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Introduce init_manage_service_template interface
Date: Fri, 22 May 2015 08:33:02 -0400 [thread overview]
Message-ID: <555F21FE.8030006@tresys.com> (raw)
In-Reply-To: <20150520134345.GA21598@meriadoc.Home>
On 5/20/2015 9:43 AM, Jason Zaman wrote:
> On Wed, May 20, 2015 at 09:02:00AM -0400, Christopher J. PeBenito wrote:
>> On 5/18/2015 10:11 AM, Jason Zaman wrote:
>>> On Mon, May 18, 2015 at 03:27:48PM +0200, Sven Vermeulen wrote:
>>>> What about "operate"?
>>>
>>> or direct, govern, handle. I think operate is a bit better tho since
>>> operator is one of the standard unix accounts.
>>>
>>> Chris, do you want me to re-do the patch with any of them in particular
>>> or do you want to search and replace on your end?
>>
>> I was thinking about verbs for these interfaces in general, and obvious
>> ones are:
>>
>> * start
>> * stop
>> * <start and stop: operate, direct, govern, handle?>
>>
>> Then it occurred to me, why not do something like startstop like we do
>> sendrecv? It's ugly, but clearly indicates what is happening.
>
> That makes a lot of sense and would not have any misunderstandings. It's
> not really that ugly apart from init_startstop_service_template is pretty
> long. Do we need / want the _template in it?
It's not actually creating any types, thus it's not technically a
template, so you can skip the _template.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2015-05-22 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 22:28 [refpolicy] [PATCH] Introduce init_manage_service_template interface Jason Zaman
2015-05-18 12:57 ` Christopher J. PeBenito
2015-05-18 13:21 ` Jason Zaman
2015-05-18 13:27 ` Sven Vermeulen
2015-05-18 14:11 ` Jason Zaman
2015-05-20 13:02 ` Christopher J. PeBenito
2015-05-20 13:43 ` Jason Zaman
2015-05-22 12:33 ` Christopher J. PeBenito [this message]
2015-05-22 12:40 ` Jason Zaman
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=555F21FE.8030006@tresys.com \
--to=cpebenito@tresys.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.