[news.admin] The .rnews.lock Problem

clay@drutx.ATT.COM (Clay Lambert) (06/09/87)

	  I am having the same problem Kathy Vincent has been talking
	about; namely, with lingering .rnews.lock files that prevent
	rnews from unspooling incoming articles.  Now that we know the
	problem, has anyone figured out how it happens?

	  Trying to keep around 30 machines umm, *regular*, so to speak,
	is becoming a bit of a pain.  I'm starting with the obviously
	suspect situations (taking the machine down mid-rnews, etc.)
	and working back from there, but if anyone has already figured
	it out I'd appreciate the input.


	Clay Lambert
	ihnp4!drutx!clay

dave@lsuc.UUCP (06/10/87)

Well, for starters, you should have your /etc/rc remove locks --
all locks for all programs that commonly use them, not just
rnews.lock.  Our /etc/rc, for example, includes:

rm -f /usr/spool/lpd/??lock
rm -f /etc/ptmp	 # password-lock-file
rm -f /u/notes/.locks/*
rm -f /tmp/uucall.lock	# /usr/lib/uucp/call.often-lock-file
rm -f /usr/spool/uucp/LCK.* # uucp calling locks
rm -f /u/barad/MSLOCKDIR/*	# Empress database locks
rm -f /u/phyllis/eval/MSLOCKDIR/*
rm -f /u/fap/MSLOCKDIR/*

...and I think I'll add /usr/spool/news/.rnews.lock right now.

David Sherman
The Law Society of Upper Canada
Toronto
-- 
{ seismo!mnetor  cbosgd!utgpu  watmath  decvax!utcsri  ihnp4!utzoo } !lsuc!dave