-------- Original Message --------
Subject: monitor doesn't work in diald-0.99
Date: Wed, 12 May 1999 14:51:19 +0200 (CEST)
From: Walter Haidinger <[EMAIL PROTECTED]>
To: To:;
Hi!
Recently I upgraded to diald-0.99 and found that the monitor fifo option
did not work. After some research I found that it was _exactly_ the same
problem I had when patching diald from 0.16 to 0.16.5.
The _only_ difference is that the Linux 2.2 kernel logs "Device not
configured" instead of the 2.0 message "No such file or directory".
For those who cannot find any archives of the diald mailing list (like
me,
for instance! :-( Any references _are_ welcome!), I'm appending my old
post from Aug 3rd, 1998 below.
And while I'm at it, some other notes about diald-0.99:
* There is an '#if 1' if route.c only useful for Linux 2.0.x kernels.
If changed to '#if 0', the annoying double route entry vanishes with
kernel 2.2. Well, the comment says just this besides "FIXME"...
* The 'metric' option isn't supported by the ethertap device:
diald[5676]: start tap0: SIOCSIFMETRIC: Operation not supported
* diald-0.99 creates a default route _to_ 0.0.0.0 instead to the IP
address specified with the remote option. Is this correct?
Now, I set the default route in the addroute script manually.
* It'd be nice if the (de)initializer scripts would receive the same
arguments as the add/delroute scripts. For instance, to down the
ethertap interface in use without having to patch route.c.
So, last but not least my old post starts below.
Regards, Walter
First the good news:
I applied the 0.16.5 patches to the diald-0.16 sources and compiled
successfully. Fine.
Now for the bad: Diald-0.16.5 would not dump monitor information.
An `echo "monitor /etc/diald/modem.monitor" > /etc/diald/modem.fifo'
procduced the following syslog entries:
Aug 3 11:15:00 banshee diald[5463]:
FIFO: full monitor connection to monitor /etc/diald/modem.monitor
requested
FIFO: could not open pipe /etc/diald/modem.monitor: No such file or
directory
There cannot be any permission problems because everything (echo, diald)
were run as root. Of course fifo /etc/diald/modem.monitor does exist.
Morever, it did work with previous diald-0.16 as I did not change
anything
but compile the new diald and install it.
I solved the problem when I *removed* the patch (beginning at line 653
of
diald-patch-0.16.5) in diald.c:
@@ -431,7 +468,7 @@
if (stat(fifoname,&sbuf) < 0 || !sbuf.st_mode&S_IFIFO) {
syslog(LOG_INFO,"FIFO: %s not a pipe.",
buf+k);
- } else if ((fd = open(buf+k,O_WRONLY))<0) {
+ } else if ((fd = open(buf+k,O_WRONLY|O_NDELAY))<0) {
syslog(LOG_INFO,"FIFO: could not open pipe %s: %m",
buf+k);
} else {
That is, I cut `|O_NDELAY' and recompiled.
Now diald-0.16.5 happily dumps monitoring info again.
Can anyone dump monitor info with an unmodified diald-0.16.5 ?
--
Walter Haidinger <[EMAIL PROTECTED]>
Student of Electrical Engineering,University of
Technology,Vienna,Austria
Address: Brunnerstrasse 6,A-3108 St.P"olten,Austria.Tel.:
+43-2742-257191
PGP public key available:
http://members.pgv.at/haidinger/pgp/pubkey.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-diald"
in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
