Sorry for the confusion...
> There should not be a diald process created every time you
> connect.
> My machine creates one diald process (PID is 208) which is the only
> diald it has until the next reboot. Do this command
> ps ax | grep diald
There's only one diald process but every time diald dials, it creates
new connect and pppd processes which increases the next PID
available. These are terminated by diald as part of it's operation.
> You might also look into the vmstat and ps commands to figure out
> where your machine cycles are going.
I get this from vmstat when the machine is running slow:
procs memory swap io system cpu
r b w swpd free buff cache si so bi bo in cs us sy id
0 0 0 6140 900 404 3816 0 0 0 1 11 10 3 2 1
I've never user vmstat before - does this look right or
indicate a problem?
I'm not sure whether diald is at fault - maybe I'm just
asking too much of the server!
Regards,
Iain
Iain F. McLaren
Systems Software Engineer
Myrica (UK) Ltd
Dunfermline
Tel. 01383 627309
Email: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
