🚀 go-pugleaf

nairdo@csnaa (Nick Airdo) writes:
> I'm looking for information on the BackSpace application (running on  
> 2.2).  I was told by several people that it has some bugs which may  
> cause your NeXT to freeze, and that it wastes cpu cycles.
> 
> The reason why I need this information is because my NeXT admin is using  
> backspace on our the servers.  He refuses to believe me unless I show  
> him some documentation on the problem.  

Some modules had bugs in them.  They were quite noticable, as I remember.  I  
just don't run those modules.  

This machine is running 2.1, and has been running backspace for, oh, 95% of  
the elapsed time since BackSpace was released.  The average uptime for my  
NeXT is about 30 days.  The usual reason for a reboot is that I have to  
connect or unconnect some SCSI device, or install new software.  The last  
time it crashed or froze up was, uh, gee I don't remember.

There certainly were a few modules with bugs in them, but the ones I use  
don't seem to give me any problems.

As for wasted cycles, just change the mach priority (it's a preference  
setting in BackSpace).  This will reduce, though not eliminate, the amount  
of cycles it steals from other stuff.  You can also switch which module you  
use.  I tend to use the "Clock" module (on 2.1), which doesn't seem to use  
up much CPU time (I run KPerfMon so I can see how busy the CPU is at all  
times).  Other modules were real pigs.  Again, just avoid those modules.

--
Garance Alistair Drosehn     =     gad@eclipse.its.rpi.edu
ITS Systems Programmer            (handles NeXT-type mail)
Rensselaer Polytechnic Institute;           Troy NY    USA