davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) (11/10/89)
In article <197@isgtec.UUCP>, robert@isgtec.UUCP (Robert Osborne) writes: | Great asshole, post another couple and get this group onto our expire | nightly list, better yet post several so we can stop getting it all | together! I agree with the sentiment if not the wording of this, but I suggest that any site which it tight on disk (like most of mine) would do well to search selected groups for postings larger than N and older than M. I do this, and argive the result to backup media (which I usually reuse). This has not seemed to confuse my news system. Like: cd /usr/spool/news find comp/graphics -type f -ctime +2 -size +10 -print > /tmp/flist cpio < /tmp/flist >/dev/rst4 xargs rm -f < /tmp/flist This easy hack may stave off problems from (and of) sysadmins. -- bill davidsen (davidsen@crdos1.crd.GE.COM -or- uunet!crdgw1!crdos1!davidsen) "The world is filled with fools. They blindly follow their so-called 'reason' in the face of the church and common sense. Any fool can see that the world is flat!" - anon
paul@manray.sgi.com (Paul Haeberli) (11/12/89)
>> From: robert@isgtec.UUCP (Robert Osborne) >> >>Looks like Paul decided to take matters into his own hands; >>Full Speed Ahead, Damn the Discussions! >> >>Great asshole, post another couple and get this group onto our expire >>nightly list, better yet post several so we can stop getting it all >>together! >>I am very unhappy :-(. >>Rob. Sorry Robert, but I love it when you say that. . . . But were you unhappy before as well? OH WELL . . . . . To put this entire discussion into perspective, lets do a litle analysis of net traffic. Over the past few weeks here's a break down of the larger messages transmitted on comp.graphics: 14,872 bytes 649 lines: X11R3 Color data base. Paul Raveling from USC Information Sciences Institute Oct 20. 10,948 bytes 215 lines: Image file format discussion Allen Braunsdorf from Purdue Oct 20. 150,136 bytes 2507 lines: Seisomograms of SF earthquake. Ken Schmahl of Sun Microsystems. Sent on Oct 23. 15,701 bytes 372 lines: GPLOT CGM interpreter. Phil Andrews at Pittsburg Supercomouting Center. Oct 27 40,328 bytes 671 lines: Here's a GIF image fall.gif Paul Haeberli at Silicon Graphics Oct 31. 14,654 bytes 366 lines: INTERACT'90 Conference Announcement. R. Winder at ucl. Nov 3. 47,022 bytes 777 lines: Here's a GIF image domain.gif Paul Haeberli at Silicon Graphics Nov 7. 19,455 bytes 359 lines: Raytracing News Eric Haines at 3D/Eye Inc. 28 Oct. Notice that one message from Ken Schmahl was three times the size of one of my GIF images and also please note that the size of the accumulated discussion about transmitting images over comp.graphics exceeds 45k bytes. 45,253 bytes 997 lines: 33 messages discussing how to handle images on comp.graphics. I don't see any problem with any of these postings listed above - even the nasty little one (1,022 bytes and 29 lines) from Robert Osborne. Its interesting to compare traffic on comp.graphics to net.sources.unix: comp.sources.unix: ~317000 bytes per day. comp.graphics: ~37836 bytes per day. I'd love to see 7 images from the computer graphics community every week. If there was 1 image transmitted every day this would increase the volume from 38 Kbytes up to 80 Kbytes. There are several other news groups that easily exceed this volume. Even at a miserable 1200 baud this would take a total of 11 minutes and 6 seconds to transmit. Now tell me that horror story again about your 8 Hour network feeds . . . . . . . Why can't people wait and see if there actually IS a problem before wasting a lot of time discussing a SOLUTION to it? Paul Haeberli paul@sgi.com