Jeff,
put the config option 'debug 1' in your diald config files somewhere.
Then put something like
local2.* /var/log/diald.log
in /etc/syslog.conf.
Then restart diald and syslog to reload the config files.
This will cause diald to dump all filter matching to the file
/var/log/diald.log, which you can simply take a look at to see what is
causing diald to bring the link up. You will get lines that look
roughly like:
Aug 27 15:21:30 servername diald[1234]: filter accepted rule XX proto
YY len ZZ blah blah blah....
I took a quick look, and it appears that the rule 'XX' refers to
filter rule number XX. The rules are numbered in order as they are
encountered by diald in the config files.
Also, the end of the line in the log appears to list the ip number and
port of the source and destination machines, which you can use to
figure out the protocol.
-Chris
p.s. Once you figure out the right rules and get your problem fixed,
be sure to take the debug options back out - they will generate a LOT
of logs..
> -----Original Message-----
> From: Jeffrey P. Rudnick [mailto:[EMAIL PROTECTED]]
> Sent: Friday, August 27, 1999 12:25 PM
> To: Chris Davis; [EMAIL PROTECTED]
> Cc: Linux-Diald@Vger. Rutgers. Edu
> Subject: Diald dials on system IPL (Diald used to connect full-time)
>
>
>
> Good news. But not 100% there yet. My diald connection problem has
> significantly improved. Thank you for your kind attention
> and suggestions.
>
> The suggestion about disabling rwhod (or ignoring its
> messages) now allows
> diald to disconnect. The last problem that I have is that
> diald still
> connects initially when my linux system boots. It
> eventually senses that
> there is inactivity and then behaves normally (connects
> when needed and
> disconnects when not).
>
> Do you have any ideas how I can overcome this initial unnecessary
> connection? Perhaps there is still some message that is
> being sent out --
> How can I track this down? At least so that I know the
> reason that it is
> dialing?
>
> Any additional suggestions are appreciated.
>
> Regards,
> Jeff Rudnick
>
> > -----Original Message-----
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> Chris Davis
> > Check /etc/services for port number/protocol assignments:
> >
> > $ grep 513 /etc/services
> > login 513/tcp
> > who 513/udp whod
> >
> > So I would suspect you have the whod daemon running,
> which broadcasts
> > info for the rwho and ruptime programs (I believe).
> >
> > -Chris
> >
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]