Are you specifying a device in your diald.conf? Post your diald.conf
here....
On Sun, 8 Aug 1999, Bonez wrote:
> Hi there,
>
> On the same note of the modprobe saying
>
> 'modprobe : can't locate module xxxN'
>
> I am getting the same problem during bootup on my systsme except that it is
> not just for on the tap0-tap15 devices but also on the eth0-eth50 and
> lo0-lo30 devices. Its like if diald is trying to find all the devices on whic
> to listen. Please note that to load diald on start up I have it contained at
> the end of the rc.sysinit script on my system. I know this is probably a
> better way to load daemons up but I haven't got round to doing it yet ;)
>
> Anyway if anyone has an suggestions on this I would really like to know.
>
>
> Much thanks - Bonez
>
>
> -
> 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]
