Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site Cascade.ARPA Path: utzoo!linus!decvax!decwrl!CSL-Vax!Cascade!reid From: reid@Cascade.ARPA Newsgroups: net.news.b Subject: expire takes 73 minutes of cpu?!?!? Message-ID: <1069@Cascade.ARPA> Date: Fri, 2-Nov-84 11:14:19 EST Article-I.D.: Cascade.1069 Posted: Fri Nov 2 11:14:19 1984 Date-Received: Sat, 3-Nov-84 21:36:20 EST Distribution: net Organization: Stanford University Lines: 29 We run 2.10.2 news, essentially as distributed in net.sources. Lacking any particular documentation on expire except the out-of-date man page that came with 4.2BSD, and reading through the source for expire enough to see that it is not obvious, I have been doing my expiring in the following way: % grep expire /usr/adm/daily.sh /usr/lib/news/expire -n arpa.unix-wizards -e30 -a /usr/lib/news/expire -n net.sources -e15 -a /usr/lib/news/expire -e30 -n all /usr/lib/news/expire -n net.singles -n net.flame -n net.politics -n net.religion -e10 This seems to more or less work, though it has left some very strange things in my history files from time to time. My complaint is that it takes 3 hours of wall clock time and 73 minutes of CPU time on an idle 750 to run these 4 expire commands: % lastcomm expire | head -8 expire S news __ 762 secs Fri Oct 26 07:40 expire S news __ 2258 secs Fri Oct 26 06:38 expire S news __ 681 secs Fri Oct 26 05:54 expire S news __ 720 secs Fri Oct 26 04:55 expire S news __ 536 secs Thu Oct 25 06:58 expire S news __ 2454 secs Thu Oct 25 05:29 expire S news __ 253 secs Thu Oct 25 05:13 expire S news __ 294 secs Thu Oct 25 04:54 Does everybody's expire take this long? If not, what am I doing wrong? If so, does anybody but me think this is too much?