While I'm definately interested in the statistical reporting, I do have one suggestion:
Add a random "sleep" time to the update. Otherwise, the reporting server is gonna get HAMMERED once a month, assuming this project gains any kind of momentum. A random sleep timer at the beginning of the script over (for example) a 3 hour window could make the load bearable for the checkin server. Just something to consider. > > I've now committed v2.0 of the 300.statistics periodic script ... this one > adds the device reporting that we'd talked about previously, and the > summary reports now reflect the driver(s) in use for those deciding to > report ... > > This Phase of the script is optional, and not enabled by default ... I > can't think of any reason why you wouldn't want to report it, but just in > case someone feels it poses a problem, its an opt-in report ... > > pkg-message updated to reflect the extra line you need to add to > /etc/periodic.conf: > > monthly_statistics_report_devices=yes > > I've written it to report driver + chip= information from pciconf -l, > since even pciconf -lv doesn't seem to use card= ... the summary report > will be extended next to show both vendor and chip statistics ... > > Let me know of any problems ... > > ---- > Marc G. Fournier Hub.Org Networking Services > (http://www.hub.org) > Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] > Yahoo . yscrappy Skype: hub.org ICQ . 7615664 > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
