On 26 Jan 1999, Jim Hague wrote:
> 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.
Oops!. When I typed _POSIX_PRIORITY_SCHEDULER in diald.h I really
meant to type _POSIX_PRIORITY_SCHEDULING but my subconscious spotted
the opportunity to save a character :-).
> Oh, and dctrl now requires the fifo to be set on the command line, whereas
> previously it would default to /etc/diald/diald.ctl.
This was intentional. If you want dctrl to start up ready
connected use the command line. Otherwise use the connect menu
option. If you *really* want you can edit the script - but you
must realise that that only makes sense for people who only
have a single diald running at one time. Even on my home system
I have two.
> 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.
Since diald snoops the interface to watch the traffic it depends
on the speed of the interface and the utilization. I suspect there
may be space for some improvement but it has to do a fair amount
of work on every packet.
Mike
--
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: [EMAIL PROTECTED] |
| 280, Silverdale Road, Earley, | Voice: +44 118 926 6996 |
| Reading RG6 7NU ENGLAND | Work: +44 118 989 0403 |
`----------------------------------------------------------------------'
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
