Re: Problems with deschall Unix client?

Nelson Minar (nelson@media.mit.edu)
Fri, 23 May 1997 14:06:41 -0400


It's amazing how deschall reveals what people don't understand about
how computers work. Wearing out CPUs. Low priority processes pigging
machines. And now, user processes crashing operating systems.

>I'd like to know if anyone has had any trouble with the deschall Unix
>client.

None at all.

>One of the SUNs at work crashed while this was running, and they
>subsequently terminated the deschall project throughout the building,
>believing it was the cause of the crash.

This is ridiculous. If a user process as simple as deschall can crash
a Unix kernel then that Unix is severely broken. Unix isn't Windows.
OTOH, if the Unix system is truly that broken and I were sysadmin I
would probably try to get people not to run programs on it, either.

btw, to answer another person's question. 30% usage on a loaded
machine for a process at nice 19 is strange. Maybe that Unix's
scheduler is bad? On a fully loaded Linux 2.0 machine deschall gets 1%
CPU. That's still too much for my tastes (especially when you factor
in context switch overhead), but it's pretty small.