[ https://issues.jboss.org/browse/WFLY-4570?page=com.atlassian.jira.plugin.... ] Karel Černohorsk commented on WFLY-4570: ---------------------------------------- [~gesker]: The service starts fine with symbolic link to the configuration file (e.g. /etc/default/wildfly -> /opt/wildfly/bin/init.d/wildfly.conf). But for the script (e.g. /etc/init.d/wildfly -> /opt/wildfly/bin/init.d/wildfly-init-debian.sh) it needs a hard link (at least, or a plain copy). With symlink it fails to see functions included by `. /lib/lsb/init-functions`. [~guirald]: There's no need to rewrite the script, the functions `pidofproc` and `log_*` are available on Ubuntu and included from `. /lib/lsb/init-functions`. The issue stems probably from some user / env issue (root vs. wildfly) by symlinking the script. And, such a simple replacement of pidofproc by pidof (as in your script version) is not quite reliable / complete, due to status codes mismatch. -- This message was sent by Atlassian JIRA (v6.4.11#64026)