Yes, simplifying the output for non-interactive mode is what the change
is about.
On 5/20/11 8:06 AM, Alexey Loubyansky wrote:
Ok, so we can divide commands by local and remote. cd, ls, etc would
belong to local. And those that translate to operations would fall into
remote.
Connect is actually not clear in this sense since it does connect to a
possibly remote server and verifies whether it's standalone or domain by
sending an operation request. The fact that the message is logged not
from the command handler is an implementation detail (it should be
logged from the handler).
So, ok, we could have an option to log only "remote" commands.
About interactive and non-interactive mode. That's kind of what I meant.
I.e. in non-interactive mode (i.e. with the presence of 'command',
'commands' or 'file') we could log only the commands specified in one of
these arguments. Would this be enough?
Having "quiet" mode meaning not to log "connected/closed" seems like
too
much to me.