[Slackbuilds-users] Note in bitlbee SBo regarding configuration
erectlocution at gmail.com
Fri May 30 19:09:00 UTC 2008
Hi, Alex & Mark,
On Fri, May 30, 2008 at 07:46:46PM +0200, Aleksandar Samardzic wrote:
> On Fri, May 30, 2008 at 6:59 PM, Mark Walling <mark at markwalling.org> wrote:
> > On 05/30/08, Daniel Black wrote:
> >> Hi, folks,
> >> The configuration note for the bitlbee SBo suggests the user add the
> >> following to inetd.conf:
> >> 6667 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee
> >> I tried this, and could not connect to bitlbee. /var/log/secure logged
> >> connection refusals. I poked around bitlbee's docs, and they recommend
> >> the following:
> >> 6667 stream tcp nowait nobody /usr/sbin/bitlbee bitlbee
> >> With this, upon restarting inetd, I connected without issue. I'm
> >> running stock 12.1, so I imagine this is the case with most anyone. Is
> >> this a change that should be made in the SBo documentation?
> > FWIW, I've been running Bitlbee here with tcp_wrappers with no problems:
> > /etc/inetd.conf
> > 6668 stream tcp nowait nobody /usr/sbin/tcpd /usr/sbin/bitlbee
> I should have been more detailed with my previous message, and note
> there that I too was able to connect to the daemon using
> /etc/inetd.conf configuration as suggested in given SlackBuild README
> file. Also, I should have read OP message more carefully - indeed it
> looks like TCP wrappers problems (so maybe /etc/hosts.allow and
> /etc/hosts.deny files should be checked on given machine?)...
Hmm. I actually had thought of some PEBKAC on hosts.allow, after looking at /var/log/secure. I suppose my attempted fixes were off. Apologies for spamming the list without confirming my configuration wasn't to blame.
Thanks for the responses.
More information about the SlackBuilds-users