[
https://issues.apache.org/jira/browse/KARAF-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13407003#comment-13407003
]
Guillaume Nodet commented on KARAF-1627:
----------------------------------------
Be aware that the {{karaf.startRemoteShell}} and {{karaf.startLocalConsole}}
system properties are used from within the bin/karaf shell scripts to control
the behavior (without being persistent and change the config). I think this
needs to be kept this way, so I'm not sure there is much to gain to be able to
dynamically start / stop the ssh server, it's really easy to start/stop the
bundle instead.
> Remove sshd command and instead make sshd react directly to config changes
> --------------------------------------------------------------------------
>
> Key: KARAF-1627
> URL: https://issues.apache.org/jira/browse/KARAF-1627
> Project: Karaf
> Issue Type: Bug
> Components: karaf-shell
> Reporter: Christian Schneider
> Assignee: Christian Schneider
> Fix For: 3.0.0
>
>
> Currently the start of sshd is controlled using
> "system.properties" there we have the attribute
> "karaf.startRemoteShell" which can be true or false. The problem with this is
> that changes do not make sshd react directly. You have to restart karaf.
> So we have the sshd command which can also start the ssh server. The problem
> with the command is that it can only start the server but not stop it. It
> also start a new server with each call.
> I propose we remove the sshd command and instead move the attribute to
> control the start into org.apache.karaf.shell.cfg. This is already read using
> config admin and changes are reflected in real time.
> I propose the attribute sshdStart=true|false with default to true.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
