roy@phri.nyu.edu (Roy Smith) (11/21/89)
One of the sites I feed news to has asked me to turn off news for a
little while because his /usr/spool is too full. What's the best way to do
that? I just put a line in /usr/lib/news/batchparms with 0 for the third
field (queue length). Was this the right thing to do? What I used to do
in cases like this under B news was to edit the sys file, but that's always
a mess so I don't like to play with it any more than I have to.
--
Roy Smith, Public Health Research Institute
455 First Avenue, New York, NY 10016
{att,philabs,cmcl2,rutgers,hombre}!phri!roy -or- roy@alanine.phri.nyu.edu
"The connector is the network"henry@utzoo.uucp (Henry Spencer) (11/22/89)
In article <1989Nov20.160329.7715@phri.nyu.edu> roy@phri.nyu.edu (Roy Smith) writes: > One of the sites I feed news to has asked me to turn off news for a >little while because his /usr/spool is too full. What's the best way to do >that? I just put a line in /usr/lib/news/batchparms with 0 for the third >field (queue length). Was this the right thing to do? This will work, sort of -- it will suspend batching to him, but will continue to queue up the names of news articles. I.e., he'll have a big backlog when you re-enable batching, although many of the articles will have expired. (This can be a problem because the current batcher has trouble dealing with this sort of situation efficiently.) You haven't really turned off the feed to him, just postponed it. >What I used to do >in cases like this under B news was to edit the sys file, but that's always >a mess so I don't like to play with it any more than I have to. I think that's still the preferred way to do the job. What I do in such cases is comment out the sysfile line, which makes it easy to put it back later. -- A bit of tolerance is worth a | Henry Spencer at U of Toronto Zoology megabyte of flaming. | uunet!attcan!utzoo!henry henry@zoo.toronto.edu