> Does anyone know why I get the following log when starting diald on my RH
> 5.2 (2.0.36) box:
> Aug 1 02:42:47 zadkiel diald[1790]: Creating FIFO
> Aug 1 02:42:47 zadkiel diald[1790]: start sl0: SIOCSIFMETRIC: Invalid argument
> Aug 1 02:42:47 zadkiel diald[1790]: start sl0: SIOCSIFMTU: Invalid argument
> Aug 1 02:42:47 zadkiel diald[1790]: FIFO closed
I get the same error messages! I'm using a 2.2.5 kernel and the
Redhat 6.0 glibc2.1 libs.
I *think* that these error messages are coming from the "route"
command. That is, I'm pretty sure diald is invoking "route" at the
switchover with some outdated or invalid commands. I've seen error
messages similar to these when trying to configure a route using a
misconfigured network interface.
I'm not sure about the SOICS part, but IFMETRIC stands for
Interface Metric, and IFMTU is Interface MTU (Maximum Transmission Unit).
Both of these are network interface configuration options.
I think the solution is to wade through the diald code and see how
and where it is invoking "route" (and perhaps "ifconfig"?) and look at the
options it is using. Unfortunately, I don't have time to do that right
now, and the error messages *seem* fairly harmless.
--Derek
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
