Open Stack

On Tue, May 07, 2013, Mark McLoughlin <markmc at redhat.com> wrote:
> I think you hit the nail on the head with "the relative permanence of
> each".
> 
> With a service started by the likes of systemd, the command line
> arguments are the most permanent - you're much more likely to change the
> config file than the command line arguments used by the service.

Seems like a packaging bug with that distribution then.

Why is it using two different ways to configure the service? Especially
if one is more difficult to change than the other?

This is especially bad because user's (rightfully or not) already have
an expectation that command line arguments override config files.

JE