Triffic to see some action on the diald front. Thanks for your efforts Mike.
A couple of comments and couple of questions.
> I can understand why the setnev of DIALD_LINK might fail
> if you haven't got a "linkname xxx" in your config but the
> MODEM one happens first and that one has always been there.
> Current_dev shouldn't be null or bogus or you would have died
> earlier - unless it has been trashed somewhere. The only
> other thing would be your environment getting trashed.
> Unfortunately it all seems to work for me :-(.
I had the 'crash on connect' problem. It turned out as you suggested to be not
having a linkname when setting DIALD_LINK. You may have done this already,
but can you check for this so that existing conf files will work unmodified?
Meanwhile, a question. _POSIX_PRIORITY_SCHEDULER - is this already set on your
system, or do you set it in the Makefile? I tried setting 'scheduler other'; it
fails with a 'scheduler must be fifo, rr or other' message if
_POSIX_PRIORITY_SCHEDULER isn't defined. 'other' should probably always succeed.
Oh, and dctrl now requires the fifo to be set on the command line, whereas
previously it would default to /etc/diald/diald.ctl.
Second question - how much load does everybody see diald putting on the system?
I've running it on a lowly 486/100, and when suck is doing its thing my load
average goes spinning up to 7-8. I think suck is responsible for most of this,
but I do see diald taking 30-40% of the CPU.
---
Jim Hague - [EMAIL PROTECTED] (Work), [EMAIL PROTECTED] (Play)
Never trust a computer you can't lift.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
