On 05/03/07 20:04, Garrett D'Amore wrote:
If the device isn't in use, then probably the historical data simply is not interesting.
They could be useful in post-mortem debugging where they represent a small handle on past history relative to the snapshot-in-time which the system crash dump represents. So I'd suggest the solution is not to eliminate persistent kstats from the OS entirely, but instead to find a simple mechanism to detect when they are acting obstructively (as in the case you describe) rather than as a history mechanism, and to cleanup in those case or allow the driver some means to force the cleanup. Gavin _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
