scott@clmqt.marquette.Mi.US (Scott Reynolds) (09/01/89)
A quick question for those more knowledgable than I, but first some background: I am running B news 2.11.17 on a Xenix 286 box and I have noticed that at times expire seems to behave strangely. I say "seems to" because I have never been able to pinpoint exactly what the problem is; just that articles sometimes don't expire properly and other times they do. Invoking expire -r always fixes this temporarily, but I lose all of my cancelled article info. I have compiled they system with the dbm library. I notice that my history.pag file has grown up to be a substantial chunk of bytes; nearly 2MB to be exact. My ulimit defaults to 4096, so I'm just under the wire, but what would happen if expire tried to expand the dbm file? Now, I know that a database generated by dbm has "holes" in it, and therefore that 2MB file is probably nowhere near that size (I have reason to believe it's actually more like 1.5MB of data) but I can't seem to find anything in the manuals regarding the relationship between dbm and ulimit. I'm not sure if another problem I'm having is related, but it seems to be somewhere in the news software. Whenever I get a good-sized batch in here and the history file is big, somebody eats up all of my process table entries... help?! I have already set ulimit higher for the expire. -- Scott Reynolds rutgers!mailrus!clip!clmqt!scott Enterprise Information System scott@clmqt.marquette.Mi.US "Insufficient facts always invite danger." -- Spock