Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!iuvax!cica!tut.cis.ohio-state.edu!dinosaur.cis.ohio-state.edu!karl From: karl@dinosaur.cis.ohio-state.edu (Karl Kleinpaste) Newsgroups: news.software.b Subject: B news unmanageable? Message-ID: Date: 11 Jul 89 01:34:45 GMT References: <1989Jul10.195611.9665@pcrat.uucp> Sender: news@tut.cis.ohio-state.edu Distribution: na Organization: OSU Lines: 22 I almost hate to ask this question; it seems too prone to starting a flame fest, or perhaps a massive b*tch-and-moan session, neither of which interests me particularly. Nonetheless, this note prompts me to ask... [rick@pcrat.uucp:] BTW, C news wasn't any panacea here, even with DBZ... It *does* seem more manageable, though, than B news. I am curious (truly, just _curious_) as to what in B news people find "unmanageable." Define "unmanageable" in whatever terms suit you in your context. I find B news really quite manageable. What I need are tools for hacking on the configuration files more mechanically, e.g., adding a new feed requires me to edit sys, nntp_access, and nntpsend. Alternatively, sys, Systems, Permissions, and newsbatches (local script which does UUCP batching). Otherwise, it needs relatively little care in terms of daily monitoring/management. I run report.awk every night so I get activity summaries; I expire once a week on a 3-week basis; I use trimlib to keep the number of logfiles to a manageable set (just the last 2 days or so); little else. Where do others find that B news eats your time for "management"?