Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!psuvm!ysub!temngt23 From: TEMNGT23@ysub.ysu.edu (Lou Anschuetz) Newsgroups: comp.sys.ncr Subject: braindead (again), prf and streams Message-ID: <90330.082142TEMNGT23@ysub.ysu.edu> Date: 26 Nov 90 13:21:41 GMT Organization: Youngstown State University VM system (YSUB) Lines: 43 This is sort of a followup to my prior question about my often braindead tower 32/700. It did indeed die the same way three times over the holiday weekend, requiring a 140 mile drive at one point to come back and fix it. Again, no error message, just a login prompt and no response. This phenomenon appears to be related to some problem with getty's, but is impossible to diagnose. Any help would be appreciated. Second, we are considering buying a terminal server (16 port) to do away with HPSIO systems. Anyone have a good (cheap) recommendation on one that will perform dedicated access to to the tower (ie: a dial in to the server should automagically connect you to the tower and not give you an annex prompt only). Second, prf is a mystery. I can create a file called /dev/prf, which does not exist and thus allows no use of the profiler. With this done prfld complains that no value is set for prfmax (and indeed there is no parameter for this in the makefiles), and prfstat on complains that there is a -1 return code from the kernel. BTW, prfstat on also reports that it turns ON the statistics. Third, I have the normal 380 NBLK16 assigned. From time to time I get a report of 10 or 11 failures on this value, even though the max used is never over about 285. This may be a dumb question, but how can this be? This is even more puzzling since there are plenty of spare 64byte blocks which never fail? Finally, netstat has become completely broken. If I am real lucky it reports 1 second of time used, but never returns (after printing the column headers). Most times it reports 0 time used. Is there something besides netstat (I have reloaded it from the install tape) and /tmp/netstatdata that is required for this program to work? I know that this was a problem in 4.00 of win tcpip, but I thought it was fixed in 4.01. Indeed, it was working correctly up until last Tuesday, though it was still terribly slow for a function that should be reading a memory value.... Sorry if some of this sounds angry, I'm just tired from driving in every night over the weekend to power off the machine, power it on, say no to dumping to tape, powering off, powering on, going into single user, fsck, and finally getting up and going..... :-( Lou Anschuetz temngt23@ysub.ysu.edu root@yfn.ysu.edu