wezel@balaena.UUCP (Jos C. van Wezel) (08/19/88)
Followup-To: Distribution: world Organization: Biology Dept., Free Univ., Amsterdam, The Netherlands. Keywords: A question to the community, I have News (2.11B) up and running for about three months now, but a irritating misbehaviour keeps popping up. When I try to expire with a crontab like: /<libdir>/expire -e 7 -E 8 nothing happens, at least no expiration of articles. Sometimes the message "Cannot get/set lockfile" is logged, but every permission is OK and the only cause I can think of is that expire was started while inews was still busy (some downloads take a while). Furthermore the history file does NOT seem to be touched, after an expire run. Until now I did the following manually to retrieve my i-nodes ( since nothing expires, things tend to pile up): expire -r -I -e 7 expire -n all This releaved the disks eventually, but I never used it overnight because of the unexpected and long time it takes to run. My question therefore is: what does expire need to expire or what could have gone wrong setting up the News. I'm running SysV 3.1 with News 2.11B p14. Thanks for any suggestions. Jos van Wezel wezel@bio.vu.nl .....mcvax\!botter\!balaena\!wezel
reid@decwrl.dec.com (Brian Reid) (08/21/88)
Check to make sure you aren't running expire with DEBUG enabled. When you turn on debug mode, it doesn't actually expire anything. (This can be extremely annoying if what you are trying to do is debug its non-expiring behavior).
hack@bellboy.UUCP (Greg Hackney) (08/22/88)
In article <451@balaena.UUCP> wezel@balaena.UUCP (Jos C. van Wezel) writes: If this does nothing: > expire -e 7 -E 8 And this works: > expire -r -I -e 7 > expire -n all It sounds like the articles are missing from the history file, and therfore can't expire them. In the second case, the history file is first rebuilt. So might the problem be with inews rather than expire? -- Greg