You are not logged in.
Pages: 1
Before I file a bug-report: has anyone else experienced bitlbee failing after the latest xinetd-update? It worked before for me and now it simply does not. No connection possible, nothing. Anyone else got that problem?
Todays mistakes are tomorrows catastrophes.
Offline
Yep, you now have to allow the loopback interface in your /etc/hosts.allow file:
bitlbee: 127.0.0.1
Offline
Thanks heaps, elasticdog! It should have been mentioned during the update IMHO. Ah well. Thanks again.
Todays mistakes are tomorrows catastrophes.
Offline
While I don't run bitlbee anymore (it doesn't support jabber transports), I used to run it in the "OMG UNSAFE" daemon mode just fine... in fact, I never even used it with xinetd.
Offline
What can I say? You are just such a daredevil.
Todays mistakes are tomorrows catastrophes.
Offline
hey now, I only package it to use xinetd because the bitlbee devs themselves seem to think daemon mode is zomg unsafe...
The suggestion box only accepts patches.
Offline
It's not your fault neotuli. phrakture, leave him alone, you evil man! Well, what should you expect from Skeletor anyway?
Last edited by mucknert (2007-02-09 18:09:49)
Todays mistakes are tomorrows catastrophes.
Offline
hey now, I only package it to use xinetd because the bitlbee devs themselves seem to think daemon mode is zomg unsafe...
Yeah, but my edge is bleeding
Offline
Pages: 1