Date: Sun, 26 Nov 2000 10:10:22 +0100 (MET) From: Martin Husemann <martin@duskware.de> To: Stefan Walter <stefan.walter@stud.udo.edu> Cc: freebsd-isdn@freebsd.org Subject: Re: No connection with isdnmonitor Message-ID: <200011260910.eAQ9AMX00502@night-porter.duskware.de> In-Reply-To: <Pine.BSF.4.21.0011251541190.320-100000@dunkelkammer.void> "from Stefan Walter at Nov 25, 2000 03:48:47 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Well, yes: it doesn't work, either. ;) I did try it, but the > socket is not created by isdnd. Additionally - although I'm not > quite a newbie to UNIX systems any more -, I know next to nothing about > sockets; just enough to make sure it doesn't work, either. Please try this: shut down isdnd, start it again manually. Then look at the place where it should have created its socket (i.e. /var/run/isdn-monitor). If it's there, then probably your isdnd is started too early at boot time and the socket is removed by /var/run cleanup later. You could also see this from netstat: it would list the socket, even if its not in the filesystem. > netstat says there's nothing listening on port 451 at any of my IPs. I > tried 127.0.0.1 as well as the IP of my NIC, plus the local domain > socket. That's why I was asking, everything seems well-configured... So, either you don't have montior support (or TCP/IP montior support) compiled into your isdnd (check for I4B_EXTERNAL_MONITOR and I4B_NOTCPIP_MONITOR on the cc command line when compiling isdnd), or your isdnd should have loged all socket relevant errors when starting up. Or: something in your config file is wrong (or a bug in the parser reads it wrong) and therefore isdnd doesn't even try create a monitor socket. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200011260910.eAQ9AMX00502>