Path: utzoo!utstat!news-server.csri.toronto.edu!cs.utexas.edu!chinacat!chip From: chip@chinacat.Unicom.COM (Chip Rosenthal) Newsgroups: news.software.b Subject: Re: Monitoring group volume and popularity Message-ID: <1559@chinacat.Unicom.COM> Date: 7 Sep 90 15:30:44 GMT References: <1990Sep7.101916.1849@bhpcpd.kembla.oz.au> Organization: Unicom Systems Development, Austin, TX Lines: 39 In article <1990Sep7.101916.1849@bhpcpd.kembla.oz.au> bernd@bhpcpd.kembla.oz.au (Bernd Wechner) writes: >Specifically it should produce a log (perhaps daily or weekly) of >each newsgroup and how much disk space it is using (preferably sorted by >size), and how many people are known to be reading that group. Nightly, I run an "ngsizes" report which gives me not only this information, but also a breakdown of usage in the newsgroup by age. Here's a sample: +--------------------------------------------------------------------------- | newsgroup read 0days 1days 3days 5days 7days 15days | rec.arts.movies 1 1070 550 4 4 4 4 | rec.arts.sf-lovers 1 846 544 30 0 0 0 | news.groups 1 834 198 0 0 0 0 | news.lists 1 732 58 0 0 0 0 | news.announce.newusers 3 700 0 0 0 0 0 +--------------------------------------------------------------------------- i.e. "rec.arts.movies" has one reader and uses 1070 disk blocks. Of that 1070, 550 are from articles >=1 day old, and 4 are from articles >=15 days. The "ngsizes" script uses a "du" reimplimentation I wrote. I originally wrote it to add some features to du, such as the breakdown by age and the ability to not accumulate subdirectory usage (i.e. don't count alt/sources/d's usage in alt/sources). An unexpected result of this is that my "du" is not only significantly faster than a couple of standard du's I looked at, it also fixed some bugs. In particular, I looked at SCO XENIX 2.3 and ISC UNIX 2.0.2. Both of these reported wrong results for directories with very large files. Drop me a line if you are interested in this stuff. If there are enough requests, I'll post. (Note - this "du" runs in a SysVish environment. For example, you must have an statfs(2).) -- Chip Rosenthal Unicom Systems Development, 512-482-8260 Our motto is: We never say, "But it works with DOS."