Bug 301082 – net-im/bitlbee-1.2.4: drop bitlbeed init-script, provide one for bitlbee

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Stijn Tintel 2010-01-15 12:57:25 UTC]

There is no init script for bitlbee. There seems to be one for bitlbeed, but using that results in unexpected behavior.

There is RunMode = ForkDaemon now anyway, so imho the whole bitlbeed thing should go away. Or it should at least error when RunMode != inetd, which is needed to run bitlbee with bitlbeed.

Reproducible: Always




For now I just used the bitlbee init-script that comes with Debian, works fine.

[Comment 1 Cédric Krier 2010-02-28 15:49:04 UTC]

Fix in CVS

[Comment 2 konsti 2010-03-04 14:25:30 UTC]

So /etc/init.d/bitlbeed moved to /etc/init.d/bitlbee recently? Inspecting the init scripts and trying to run it not listening on default port but another, is it possible /etc/conf.d/bitlbeed vanished and /etc/conf.d/bitlbee not being used anymore?

[Comment 3 Cédric Krier 2010-03-04 18:12:54 UTC]

(In reply to comment #2)
> So /etc/init.d/bitlbeed moved to /etc/init.d/bitlbee recently? Inspecting the
> init scripts and trying to run it not listening on default port but another, is
> it possible /etc/conf.d/bitlbeed vanished and /etc/conf.d/bitlbee not being
> used anymore?
> 

There was a bug in the init script.
It is fixed in CVS now.