Package: jabber-irc
Version: 0.4cvs20080505-1.1
Severity: important
Dear Maintainer,
It seems that the init script doesn't start jabber-irc at all.
It doesn't event report any error.
As you can see below, I "fixed" this problem by removing the "-c
+jabber:adm" option to the start-stop-daemon function.
Because I don't understanf very well init script, it musn't be the right
+way however.
Regards,
Xavier
-- System Information:
Debian Release: 7.0
Architecture: armhf (armv6l)
Kernel: Linux 3.6.11+ (PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages jabber-irc depends on:
ii adduser 3.113+nmu3
ii lsb-base 4.1+Debian8+rpi1
ii python 2.7.3-4
ii python-irclib 0.4.8-1
ii python-xmpp 0.4.1-cvs20080505.2
jabber-irc recommends no packages.
Versions of packages jabber-irc suggests:
pn jabber <none>
-- Configuration Files:
/etc/default/jabber-irc changed:
ENABLED='1'
/etc/init.d/jabber-irc changed:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/jabberd-irc
CMDLINE=/usr/bin/python/usr/sbin/jabberd-irc
NAME=jabber-irc
DESC=jabber-irc
ARGS=''
PID=/var/run/jabber/$NAME.pid
ENABLED='0'
if [ ! -d /var/run/jabber ] ; then
mkdir /var/run/jabber
chown jabber:adm /var/run/jabber
chmod 0775 /var/run/jabber
fi
if [ -f /etc/default/jabber-irc ]; then
. /etc/default/jabber-irc
fi
. /lib/lsb/init-functions
test -x $DAEMON -a "$ENABLED" -eq "1" || exit 0
set -e
case "$1" in
start)
if [ -e $PID ]; then
PIDDIR=/proc/$(cat $PID)
if [ -d ${PIDDIR} -a "$(cat ${PIDDIR}/cmdline)" = "$CMDLINE" ]; then
log_success_msg "$DESC already started; not starting"
exit
else
log_success_msg "Removing stale PID file $PID"
rm -f $PID
fi
fi
log_daemon_msg "Starting $DESC: "
export PID
start-stop-daemon -b --start --quiet --pidfile $PID\
--make-pidfile --exec $DAEMON -- $ARGS
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
start-stop-daemon -o --stop --signal INT --quiet --retry 3 \
--pidfile $PID --exec /usr/bin/python
echo "$NAME."
rm -f $PID
;;
#reload)
#
# If the daemon can reload its config files on the fly
# for example by sending it SIGHUP, do it here.
#
# If the daemon responds to changes in its config file
# directly anyway, make this a do-nothing entry.
#
# echo "Reloading $DESC configuration files."
# start-stop-daemon --stop --signal 1 --quiet --pidfile \
# /var/run/jabber/$NAME.pid --exec $DAEMON
#;;
restart|force-reload)
#
# If the "reload" option is implemented, move the "force-reload"
# option to the "reload" entry above. If not, "force-reload" is
# just the same as "restart".
#
$0 stop
sleep 3
$0 start
;;
*)
N=/etc/init.d/$NAME
# echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
exit 0
/etc/pyirct.conf.xml changed:
<?xml version="1.0" ?>
<pyirct>
<!-- This file contains options to be configured by the server
administrator. -->
<!-- Please read through all the options in this file -->
<!-- The JabberID of the transport -->
<jid>irc.yeuxdelibad.net</jid>
<!-- The component JID of the transport. Unless you're doing clustering,
leave this alone -->
<!-- <compjid>irc1</compjid> -->
<!-- The public IP or DNS name of the machine the transport is running on
-->
<!-- This is used to select the outgoing IP address used to connect to IRC
networks -->
<!-- otherwise known as the vanity address, it's safe to leave it
commented -->
<!--<host>vanity.host.example.net</host>-->
<!-- The name of the transport in the service discovery list. -->
<!-- <discoName>IRC Transport</discoName> -->
<!-- The location of the spool file.. if relative, relative to the PyIRCt
dir. -->
<!-- Include the jid of the transport, if running multiple copies of the
same transport -->
<spoolFile>ircuser.dbm</spoolFile>
<!-- The location of the PID file, relative to the PyIRCt directory -->
<!-- Comment out if you do not want a PID file -->
<pid>PyIRCt.pid</pid>
<!-- The IP address or DNS name of the main Jabber server -->
<mainServer>127.0.0.1</mainServer>
<!-- The JID of the main Jabber server -->
<mainServerJID>localhost</mainServerJID>
<!-- The TCP port to connect to the Jabber server on (this is the default
for Jabberd2) -->
<port>5347</port>
<!-- The authentication token to use when connecting to the Jabber server
-->
<secret>secret</secret>
<!-- SASL username used to bind to Jabber server. -->
<!-- secret, above, is used for sasl password -->
<!--<saslUsername>username-for-jabberd2-connection</saslUsername>-->
<!-- Allow users to register with this transport -->
<allowRegister/>
<!-- Require users to be registered before allowing them to join a room -->
<!-- <requireRegister/> -->
<!-- Send activity messages to users (for clients that don't support MUC)
-->
<activityMessages/>
<!-- Use external component binding. -->
<!-- This dodges the need to manually configure all jids that talk to this
transport. -->
<!-- Jabberd2 requires saslUsername and useRouteWrap for this to work. -->
<!-- Wildfire as of 2.6.0 requires just this. -->
<!--<useComponentBinding/>-->
<!-- Wrap stanzas in <route> stanza. -->
<!-- Jabberd2 requires this for useComponentBinding. -->
<!--<useRouteWrap/>-->
<!-- You can choose which users you wish to have as administrators. These
users can perform some tasks with Ad-Hoc commands that others cannot -->
<admins>
<jid>xav...@yeuxdelibad.net</jid>
</admins>
<!-- The file to log to. Leave this disabled for stdout only -->
<debugFile>/var/log/ircerror.log</debugFile>
<!-- Show the raw data being sent and received from the xmpp and irc
servers -->
<!--<dumpProtocol/>-->
<!-- The default charset to use for the transport, if not supplied by the
user when registering -->
<!-- <charset>utf-8</charset> -->
</pyirct>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
