shepperd@dms.UUCP (Dave Shepperd) (10/27/89)
I haven't gotten any messages in the sco.opendesktop group for weeks. This might be because our connection doesn't work anymore, so I cross posted to comp.unix.xenix in the hopes that some of the readers there are currently using SCO's ODT. 1) Who is responsible for the message "KERNEL: allocq: out of queues" Which que ran out? Is this the STREAMS que? 2) What happened to sw? The sar utility is neat but there is no option to see what's happening with the streams parameters, yet TCP and NFS say to keep an eye on the streams parameters and adjust them accordingly. 3) What does one do about NFS lockups? The system defaults to reporting disk usage at login (I have since removed it) which would hang one's login (even root) if an NFS directory was mounted but NFS was stuck for whatever reason. Why does /etc/nfs start|stop do an su to root (which waits for the root password to be typed but without a prompt) even if it is run from root already? 4) How do you crash a stuck system such that a post mortem can be performed on the corpse? How does one crash a stuck system without destroying the filesystems? Pressing reset leaves no evidence of why the system was stuck and the fsck that runs on the subsequent boot may report 100's of errors in the filesystems (but never any filenames, grrrr). The fsck info zips by on the screen faster than one can read it. Can it be placed in a file so one might have a hope in hell of finding and correcting the errors (such as restoring the files that fsck deletes or otherwise wipes out)? 5) What does one do about PANIC messages that are more than 24 lines? It has happened once while I was playing with a device driver that the system panic halted but most of the panic message (the most useful part, naturally) scrolled off the top of the screen. Nope, the message was not placed in /usr/adm/messages. 6) Where is the password file? Specifically, we don't want to use the C2 security level and we want to be able to reuse usernames/uid's. The system apparently won't let us do that anymore. 7) Who, what, when, where or why does the message "no more procs" show up when trying to open an xterm window. (xterm: error 23, errno 11: no more processes). The number of system process slots is no where near used up (maybe used 30-40 out of 75), there are no more than about 4 pttys used according to ps, but there's 16 /dev/ttyp0x's and 8 /dev/ttypx's. Other X clients will start up, only xterm fails. -- Dave Shepperd. shepperd@dms.UUCP or motcsd!dms!shepperd Atari Games Corporation, 675 Sycamore Drive, Milpitas CA 95035. When it comes time to collect the wages of sin, some of ue will get time and a half. -- Flip Wilson