Bug 662289

Summary:	bitlbee should start in Daemon or ForkDaemon mode (and we should use systemd features correctly)
Product:	[Fedora] Fedora	Reporter:	Matěj Cepl <mcepl>
Component:	bitlbee	Assignee:	Matěj Cepl <mcepl>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	mcepl, mcepl, redhat-bugzilla, vmiklos
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-07-24 21:53:54 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	666182
Bug Blocks:

Description Matěj Cepl 2010-12-11 08:12:04 UTC

Description of problem:
README describes (Fork)Daemon mode as follows:

--- (Fork)Daemon mode

These days ForkDaemon mode is the recommended way of running BitlBee. The
difference between Daemon and ForkDaemon mode is that in the latter, a
separate process is spawned for every user. This costs a little bit more
memory, but means that if one user hits a bug in the code, not all other
users get disconnected with him/her.

To use BitlBee in any daemon mode, just start it with the right flags or
enable it in bitlbee.conf (see the RunMode option). You probably want to
write an init script to start BitlBee automatically after a reboot. (This
is where you realise using a package from your distro would've been a better
idea. :-P)

Please do make sure that the user BitlBee runs as (not root, please!) is
able to read from and write to the /var/lib/bitlbee directory to save your
settings!

---------------------------------------

We are currently using inetd mode (xinetd in our case), which has been depreceated by the upstream.

If we switch to Daemon mode then we should start support (on Rawhide) systemd initialization, which would give us effectively the same delay startup as we had with xinetd. We cannot loose anything, just our shackles!

Comment 1 Matěj Cepl 2010-12-11 08:17:07 UTC

Lennart publishes his series about systemd administration on his blog http://0pointer.de/blog

Comment 2 Miklos Vajna 2010-12-27 16:48:53 UTC

Upstream ticket has a patch implementing systemd support:

http://bugs.bitlbee.org/bitlbee/ticket/738

Comment 3 Matěj Cepl 2010-12-27 21:41:25 UTC

http://koji.fedoraproject.org/koji/buildinfo?buildID=211805

Comment 4 Matěj Cepl 2010-12-29 13:13:45 UTC

We are not done yet. I have made some changes in http://pkgs.fedoraproject.org/gitweb/?p=bitlbee.git;a=commitdiff;h=a96797fa239ade673fe2e241dc9265d9da8a152c, but we need also bug 666182 (SELinux issues) to be fixed, and I needed to do these steps to get bitlbee running:

systemctl daemon-reload
systemctl enable bitlbee.service
systemctl start bitlbee.service

Not sure whether all of them are needed.

Comment 5 Matěj Cepl 2010-12-29 14:22:40 UTC

I believe complete fix from my side is at
http://pkgs.fedoraproject.org/gitweb/?p=bitlbee.git;a=commitdiff;h=3f07c5b9528d14da804cdeda750beda43c2834cd and scratch build
http://koji.fedoraproject.org/koji/taskinfo?taskID=2692585
but I will wait with the release on fixing of the blocking bug.

Comment 6 Matěj Cepl 2011-07-24 21:53:54 UTC

I think we can continue in bug 705096. Please complain there if something doesn't work.

*** This bug has been marked as a duplicate of bug 705096 ***