Opened at 2006-04-03T13:59:17Z
Closed at 2006-05-05T16:25:14Z
#129 closed enhancement (fixed)
xinetd entry for bitlbee
| Reported by: | Owned by: | wilmer | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | BitlBee | Version: | 1.0.1 |
| Keywords: | Cc: | ||
| IRC client+version: | Client-independent | Operating System: | Linux |
| OS version/distro: |
Description
The doc/bitlbee.xinetd file says, in part:
## This file assumes you have ircd somewhere in your /etc/services, if things
## don't work, check that file first.
service ircd
{
...
## xinetd is fucking retarded, what's the use of this port flag if
## it HAS to be the same as in /etc/services ?
# port = 6667
}
The purpose of that flag is to specify the port when the service is unlisted; it is not in fact necessary for the service to be in /etc/services, but you also need to specify the service "type", as in the example below.
This is my xinetd file for bitlbee. You're welcome to use it.
service bitlbee
{
disable = no
type = UNLISTED
#bind = 127.0.0.1
port = 6667
socket_type = stream
protocol = tcp
wait = no
user = daemon
server = /usr/sbin/bitlbee
log_on_failure += USERID
}
Attachments (0)
Change History (3)
comment:1 Changed at 2006-04-03T20:31:33Z by
| Owner: | set to wilmer |
|---|---|
| Status: | new → assigned |
comment:2 Changed at 2006-04-16T22:54:40Z by
00:52:28 < wilmer> I'm going to fucking burry xinetd. I have done it before and I'm going to do it again.
We know who you really are under that diguise, wilmer, or shall I say ... Steve! :o
comment:3 Changed at 2006-05-05T16:25:14Z by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Thanks! Committed in [166]. And toxik, you have interesting IRC logs. ;-)

Ahhh, so the type entry should fix the whole problem? That's great. Thanks for the info, I'll update the xinetd file soon! :-)