Garrett Wollman ha scritto:
I've looked around for examples of good practice to emulate, and
haven't found much. The closest to what I want looks to be
vboxheadless, but I'm uncomfortable with the amount of mechanism from
rc.subr that it needs to reimplement. Are there any better examples?
I'm in the process of (re)writing an rc.d script for kadmind
(security/krb5). Unlike the main Kerberos daemon, kadmind needs to
have a separate instance for each realm on the server -- it can't
support multiple realms in a single process. What I need to be able
to do:
1) Have different flags
On Tue, 2013-06-25 at 15:44 -0400, Garrett Wollman wrote:
I'm in the process of (re)writing an rc.d script for kadmind
(security/krb5). Unlike the main Kerberos daemon, kadmind needs to
have a separate instance for each realm on the server -- it can't
support multiple realms in a single
On 2013-06-25 21:44, Garrett Wollman wrote:
I'm in the process of (re)writing an rc.d script for kadmind
(security/krb5). Unlike the main Kerberos daemon, kadmind needs to
have a separate instance for each realm on the server -- it can't
support multiple realms in a single process. What I
On 2013-Jun-25, 15:44, Garrett Wollman wrote:
I'm in the process of (re)writing an rc.d script for kadmind
(security/krb5). Unlike the main Kerberos daemon, kadmind needs to
have a separate instance for each realm on the server -- it can't
support multiple realms in a single process. What I
On Tue, Jun 25, 2013 at 03:44:31PM -0400, Garrett Wollman wrote:
I'm in the process of (re)writing an rc.d script for kadmind
(security/krb5). Unlike the main Kerberos daemon, kadmind needs to
have a separate instance for each realm on the server -- it can't
support multiple realms in a
6 matches
Mail list logo
