Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0 (1.0)
Subject: Re: [krbdev.mit.edu #8607] kpropd should write a pidfile when started in standalone mode...
From: John Hascall <hascall@gmail.com>
In-Reply-To: <rt-8607-47579.14.6708577962541@krbdev.mit.edu>
Date: Tue, 22 Aug 2017 17:56:29 -0500
CC: john@iastate.edu
Content-Transfer-Encoding: quoted-printable
Message-ID: <0D37F200-9FD6-4C8B-90EE-0D42CAC92792@gmail.com>
References: <rt-8607-47579.14.6708577962541@krbdev.mit.edu>
To: rt-comment@krbdev.mit.edu
RT-Send-Cc: 
Content-Length: 975

I figured that ;)
It's just too bad nobody thought about flags consistency earlier...


John Hascall
IT Services
Iowa State Univ.

> On Aug 22, 2017, at 5:03 PM, will.fiveash@oracle.com via RT <rt-comment@krbdev.mit.edu> wrote:
> 
>> On Tue, Aug 22, 2017 at 01:47:40PM -0400, john@iastate.edu via RT wrote:
>> ...so it can be properly managed by systemctl etc.
>> 
>> I have included a sample patch to implement this.
>> NOTE: I changed the command line flags to match the other kerberos daemons
>> <https://imgflip.com/i/1uj6yv>:
>> 
>> # ./kpropd -h
>> Usage: ./kpropd [-r realm] [-s srvtab] [-dS] [-f slave_file]
>> [-F kerberos_db_file ] [-u kdb5_util_pathname]
>> [-x db_args]* [-p port] [-a acl_file]
>> [-P pid_file] (standalone mode only)
>> [-A admin_server]
> 
> Interface stability is an issue I have with this patch.  I would prefer
> a unique flag other than -P be used to provide the pid file name.
> 
> -- 
> Will Fiveash
> Oracle Solaris Software Engineer
>