Kedar Mhaswade wrote:
> Jane,
>
> I agree, but what Bill suggested is something that
> we have been wanting to do for some time. We need to do something
> to separate the options for the commands from the options for the
> asadmin program. Currently, a command implementation does not care
> what the values for:
> -- host, --port, --passwordfile, --secure, --terse etc. are.
Sort of like cvs:
$ cvs --help
Usage: cvs [cvs-options] command [command-options-and-arguments]
> All of these are "asadmin program options". A command like
> create-http-listener
> does not care about it.
And in multiline mode, you probably shouldn't be able to specify
these options on individual commands.
> A via-media solution can be reached (more specification required), if we
> say that a command name can't start with a - or a --. This is intuitive
> and can take care of our requirement.
>
> Again, think of what we want to do with this proposal. I think it is
> useful.
>
> Regards,
> Kedar
>
> PS- BTW, I am not so sure that --target is an asadmin program option. A
> command
> does care about what the value of --target is. So, the current
> discussion is
> rather unrelated with documentation of --target option.
You're probably right about that.