You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2010/01/07 11:24:54 UTC
[jira] Created: (FELIX-1970) The stop script should always work
even if the default user / password / host has been changed
The stop script should always work even if the default user / password / host has been changed
----------------------------------------------------------------------------------------------
Key: FELIX-1970
URL: https://issues.apache.org/jira/browse/FELIX-1970
Project: Felix
Issue Type: Bug
Components: Karaf
Reporter: Guillaume Nodet
Using the ssh connection to stop karaf from the stop script leads to configuration problems if the default user / password or host for the ssh connection has been changed. Furthermore, we can imagine disabling the ssh server and there would be no way to stop karaf ...
I'm planning use the same mechanism as tomcat do, i.e. create a socket bound on localhost (so that it can't be accessed from another computer) and put the socket number in a file or something like that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1970) The stop script should always work
even if the default user / password / host has been changed
Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-1970?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved FELIX-1970.
------------------------------------
Resolution: Fixed
Fix Version/s: karaf-1.4.0
Assignee: Guillaume Nodet
> The stop script should always work even if the default user / password / host has been changed
> ----------------------------------------------------------------------------------------------
>
> Key: FELIX-1970
> URL: https://issues.apache.org/jira/browse/FELIX-1970
> Project: Felix
> Issue Type: Bug
> Components: Karaf
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Fix For: karaf-1.4.0
>
>
> Using the ssh connection to stop karaf from the stop script leads to configuration problems if the default user / password or host for the ssh connection has been changed. Furthermore, we can imagine disabling the ssh server and there would be no way to stop karaf ...
> I'm planning use the same mechanism as tomcat do, i.e. create a socket bound on localhost (so that it can't be accessed from another computer) and put the socket number in a file or something like that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.