Yes, it's an initscript issue, but the init script is part of the jabberd distribution. This yet untested patch should fix the issue:
--- jabberd-2.2.5/tools/jabberd.rc.orig 2009-03-31 10:11:04.460273152 +0200 +++ jabberd-2.2.5/tools/jabberd.rc 2009-03-31 10:12:05.196309538 +0200 @@ -122,7 +122,7 @@ Start ( ) { rm -f /var/lock/subsys/${prog} rm -f ${pidPath}/${prog}.pid args="-c ${confPath}/${prog}.xml" - ${progsPath}/${prog} ${args} & 2> /dev/null + ${progsPath}/${prog} ${args} & >/dev/null 2>&1 retval=$? if [ ${retval} == 0 ]; then StatusOK
Yes, it's an initscript issue, but the init script is part of the jabberd distribution.
This yet untested patch should fix the issue:
--- jabberd- 2.2.5/tools/ jabberd. rc.orig 2009-03-31 10:11:04.460273152 +0200 2.2.5/tools/ jabberd. rc 2009-03-31 10:12:05.196309538 +0200 subsys/ ${prog} /${prog} .pid /${prog} .xml" /${prog} ${args} & 2> /dev/null /${prog} ${args} & >/dev/null 2>&1
+++ jabberd-
@@ -122,7 +122,7 @@ Start ( ) {
rm -f /var/lock/
rm -f ${pidPath}
args="-c ${confPath}
- ${progsPath}
+ ${progsPath}
retval=$?
if [ ${retval} == 0 ]; then
StatusOK