-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 13 Jan 99, at 13:47, Tommy Wareing wrote about Re: over-enthusiastic diald:
> > Disclaimer: I'm quite possibly just being too lazy here...
>
> I'll let you know once I've obeyed the FAQ.
Thanks to everybody who sent me hints on tracking down the
rogue that keeps firing up my diald connection. My apologies for
not replying to you personally, or earlier, but I've been "doing stuff"...
Since the configuration I was fighting with earlier was RH5.1, and
I'd finally figured out what values I needed to put in where, I wiped
the system, and reinstalled everything, so as not to have half-
configured arrangements lying around. That produced the
"interesting" problem that RedHat's PPP configuration *DOES
NOT* write to /etc/ppp/options. So when I installed diald, it failed to
connect to by ISP, because it didn't know what name to use. That
held things up for a while...
Bizzarely, this reinstall seems to have cleared up the problems.
Obvious culprits are therefore (this is stuff that I haven't reinstalled
over the standard 5.1 install yet):
bind-8 (RH5.1 includes bind-4)
squid
2.0.36 kernel (but I doubt it, somehow)
sound drivers.
Thanks for the restrict lines to put in my config. At least if the
rogue process does come back, it's not going to cost me anything.
So far, the winning diagnostic is:
> From: [EMAIL PROTECTED] (Giulio)
> To: "Tommy Wareing" <[EMAIL PROTECTED]>
> Subject: Re: over-enthusiastic diald
> Date sent: Wed, 13 Jan 1999 15:22:48 +0100
> Organization: nowhere
>
> On Wed, 13 Jan 1999 13:28:47 -0000, hai scritto:
>
> >The best option would be to find out what's causing the
> >connections and persuade it to stop.
>
> Start diald with debug set to 1 or while diald is running do:
> echo debug1 > /usr/lib/diald/diald.ctl
>
> then look at
> tail -f /var/log/messages
>
> (diald uses the local2 facility for logging, so if you redirected
> local2 on another file check the other file; I redirected local2 to
> /var/log/local2 just to monitor diald+dialmon+chat).
>
> and you'll see which packet brings the link up (which machine
> originates it and which port/service it is directed to).
>
> I usually start diald with debug1, then I switch debug to 0 in ip-up,
> and re-switch it to 1 with ip-down, so that I always know who is
> responsible for bringing the link up, and at the same time diald
> doesn't fill the log file with too much stuff.
>
> Ciao.
>
> --
> Giulio
> [EMAIL PROTECTED]
>
which seems to work fine, once I remembered to make the relevant
scripts executable... :-)
-----BEGIN PGP SIGNATURE-----
Version: PGP 5.5.5 -- QDPGP 2.12
Comment: http://community.wow.net/grt/qdpgp.html
iQA/AwUBNqW4TlVW4tylv9cuEQLexQCeNXWvOEoohojIDwvsBYCb80hUigsAoLMo
+AtsdX48yvywWUVXdYNQtu9c
=5tNk
-----END PGP SIGNATURE-----
--
Tommy
For PGP key, finger @trb85abc.brookes.ac.uk
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
