On 02.11.2007, at 00:52, Dave Zarzycki wrote:
On Nov 1, 2007, at 4:47 PM, Johannes Kneer wrote:
Hi
Are you making sure to run launchctl as root? Once you do, is the job already loaded? Check like so: sudo launchctl list | grep org.bitlbee.bitlbee
host:~ root# launchctl unload /Library/LaunchDaemons/ org.bitlbee.bitlbee.plist host:~ root# vim /Library/LaunchDaemons/org.bitlbee.bitlbee.plist *host:~ root# launchctl load /Library/LaunchDaemons/ org.bitlbee.bitlbee.plist bind(): Operation not permitted host:~ root# launchctl list | grep org.bitlbee.bitlbee - 0 org.bitlbee.bitlbee host:~ root# telnet 127.0.0.1 6667 Trying 127.0.0.1... host: connect to address 127.0.0.1: Connection refused host: Unable to connect to remote host host:~ root#
(I like ssh root@localhost more than sudo :)
Odd.
What does the output of "lsof -P | grep 6667" say?
host:~ root# lsof -P | grep 6667 host:~ root# launchctl list | grep org.bitlbee.bitlbee - 0 org.bitlbee.bitlbee host:~ root# lsof -P | grep 6667 host:~ root#
Do you have any firewall magic installed or configured? Is a pre- existing copy of the daemon already running?
I have! The build in one was on "set access for specific services and applications". But that's all, no ipfw stuff. If I turn it of, or if I put bitlbee manually in the list of allowed apps I can connect to it. BUT why am I not asked whether or not to allow the connection in the GUI? This feels like a GUI bug to me. But it works now. Thank you.
The bind() error means this is more of a networking problem than a launchd problem...
Cheers, Johannes