Bug 92331

Summary:	bitlbee doesn't start in daemon mode when specifed
Product:	Gentoo Linux	Reporter:	Andrew <kennerly>
Component:	[OLD] Server	Assignee:	Jason Wever (RETIRED) <weeve>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Andrew 2005-05-11 22:38:16 UTC

The init scripts fail to read or be able to select daemon mode for the bitlbee process.  When "RunMode = Daemon" is used in /etc/bitlbee/bitlbee.conf and the bitlbee process is started via /etc/init/bitlbee bitlbee is started in Inetd mode instead.

Reproducible: Always
Steps to Reproduce:
1. RunMode = Daemon in /etc/bitlbee/bitlbee.conf
2. /etc/init.d/bitlbeed start
3. Attempt connection the the daemon via IRC client


Actual Results:  
Connection refused by the daemon

Expected Results:  
Allowed connection the daemon as per the configuration file

When /usr/sbin/bitlbee is started manually, the configuration file is parsed and
correct operation ensues.

Comment 1 Jason Wever (RETIRED) gentoo-dev

2005-05-12 15:28:02 UTC

The init script (bitlbeed) is for /usr/bin/bitlbeed, whichh is designed to be a mini-inetd style server from which to run bitlbee, and starts an entirely different executable than /usr/sbin/bitlbee.  It will not work when you've set RunMode to Daemon in your configuration, and upstream suggests strongly that Daemon mode is not to be used as it is highly experimental.

Once upstream considers daemon mode to be semi-stable, I'll consider either including an additional init.d script for /usr/sbin/bitlbee or having one init.d script encompass both modes.