[
https://issues.jboss.org/browse/ISPN-5928?page=com.atlassian.jira.plugin....
]
Pierre Sutra updated ISPN-5928:
-------------------------------
Description:
The infinispan-server* scripts are not properly looking for start-stop-daemon on Ubuntu et
al. This implies that (1) the service is never called, and (2) the scripts rely on
'su' to start WildFly. As a side effect, when using ssh, the connection hangs
(because 'su' is still in background).
I suggest to use `which start-stop-daemon` to solve that problem. See patch for further
details.
Regards,
Pierre
was:
The infinispan-server* scripts are not properly looking for start-stop-daemon on Ubuntu et
al. This implies that (i) the service is never called, and (ii) the scripts rely on
'su' to start WildFly. As a side effect, when using ssh, the connection hangs
(because 'su' is still in background).
I suggest to use `which start-stop-daemon` to solve that problem. See patch for further
details.
Regards,
Pierre
WildFly init.d scripts to not find start-stop-daemon
----------------------------------------------------
Key: ISPN-5928
URL:
https://issues.jboss.org/browse/ISPN-5928
Project: Infinispan
Issue Type: Bug
Components: WildFly modules
Affects Versions: 7.2.5.Final
Reporter: Pierre Sutra
Priority: Minor
Labels: wildfly
Attachments: patch
The infinispan-server* scripts are not properly looking for start-stop-daemon on Ubuntu
et al. This implies that (1) the service is never called, and (2) the scripts rely on
'su' to start WildFly. As a side effect, when using ssh, the connection hangs
(because 'su' is still in background).
I suggest to use `which start-stop-daemon` to solve that problem. See patch for further
details.
Regards,
Pierre
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)