Bug 1257227 - socket activation for bitlbee service
Summary: socket activation for bitlbee service
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: bitlbee
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Robert Scheck
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-26 14:36 UTC by Vincent Batts
Modified: 2018-04-11 17:57 UTC (History)
3 users (show)

Fixed In Version: bitlbee-3.5-1.fc24
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-30 02:48:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Vincent Batts 2015-08-26 14:36:43 UTC 
Description of problem:
the bitlee daemon currently needs to be `systemctl enable bitlbee.service && systemctl start bitlbee`, but it could easily provide a "bitlbee.socket" that is enabled when installed. Then it is started once connected to.

Version-Release number of selected component (if applicable):
bitlbee-3.4.1-1.fc22.x86_64

an example `bitlbee.socket` (the one I use for myself):
```
[Unit]
Description=BitlBee IRC/IM gateway
Conflicts=bitlbee.service

[Socket]
ListenStream=127.0.0.1:6667
Accept=yes

[Install]
WantedBy=sockets.target
```
Comment 1 Matěj Cepl 2015-08-26 21:22:46 UTC 
That would require switching from ForkDaemon back to Daemon mode, right?
Comment 2 Vincent Batts 2015-08-27 02:28:40 UTC 
I'm not sure. I did not make those changes and it seems be fine.
Comment 3 Jan Kurik 2016-02-24 13:40:40 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 4 Robert Scheck 2017-01-30 02:48:53 UTC 
bitlbee-3.5-1.fc24 ships /usr/lib/systemd/system/bitlbee.socket meanwhile.
Note You need to log in before you can comment on or make changes to this bug.