jrg@acm.org (James R Grinter) writes:

For Solaris 2, I've been told that there exists modified serial driver that - when the OS is running - will prevent that happening.

This is in fact the standard serial/console driver in Solaris 2.6 (and 7). You'll have to set a variable in /etc/default/kbd - basically you have the option to either -react to BREAK (or L1-A, if you have a keyboard attached) - this is the default -ignore the BREAK (or L1-A).

We're running quite a few (50ish) Suns, all connected to a linux box running conserver (serial hardware being Stallion cards). We've had no problems with this so far - and we _do_ have breaks enabled, to be able to reset a machine that won't let us in for some reason.

Another thing :

I'm thinking of attending the Netapp202 course (it fits nicely in with my plans for Usenix Tech.'99) - I've been running Netapps for a few years now, but wouldn't mind some more "inside" information on the secret bits. Is anyone willing to recommend this course ?

Finally, a small tidbit for those among you who get a thrill out of (large) numbers:

We've got an F540 (current uptime: 404 days) - this box has sustained 9900 (!) NFSops/sec for 20 hours. Id' say that on average it has sustained approx 3000 NFSops/sec over the last 6 months...

NetApp needs to do something about the "total nfs ops counter" - it's rolled 15 times since the last reboot - nfsstat -l gives some really interesting output :

[output snipped] 195.225.3.37 www2.sol.no NFSOPS = 1385724634 (4294966978%)

:-)