From: Laura Conrad <lconrad@world.std.com>
Subject: Re: What is the use of /var/lock/news
Date: 15 Jan 2000 23:15:52 -0500 [thread overview]
Message-ID: <m3r9fiird3.fsf@serpent.local> (raw)
In-Reply-To: Stainless Steel Rat's message of "15 Jan 2000 22:52:31 -0500"
>>>>> "Rat" == Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
Rat> Then I suspect leafnode's NNTP server is creating the lock
Rat> files. They are created to prevent two or more instances of
Rat> leafnode or especially fetchnews from being started, which
Rat> would effectively destroy your spool.
Rat> IOW, making the lock files "go away" is a Bad Thing(tm).
Except that in my experience with fetchnews, it does sometimes leave
the lockfiles lying around when the connection gets broken
unexpectedly. What I have at the moment for dealing with this is
that in the /etc/ppp/ip-down.local script, which gets executed when
the ppp process ends, I remove any old lockfiles.
I believe that the latest leafnode distribution actually checks
whether the lockfile belongs to an existing process, and removes it if
it doesn't, so my ip-down.local removal may be unnecessary now, but
I'm pretty sure it's harmless in that context.
--
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097 fax: (801) 365-6574
233 Broadway, Cambridge, MA 02139
next prev parent reply other threads:[~2000-01-16 4:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-14 21:16 Pieter Wenk
2000-01-15 0:17 ` Stainless Steel Rat
2000-01-15 7:39 ` Pieter Wenk
2000-01-16 3:52 ` Stainless Steel Rat
2000-01-16 4:15 ` Laura Conrad [this message]
2000-01-16 9:43 ` Pieter Wenk
2000-01-16 11:09 ` Kai Großjohann
2000-01-16 19:29 ` Pieter Wenk
2000-01-16 22:20 ` Kai Großjohann
2000-01-17 6:55 ` Pieter Wenk
2000-01-18 1:32 ` Stainless Steel Rat
2000-01-18 7:30 ` Pieter Wenk
2000-01-19 2:36 ` Stainless Steel Rat
2000-01-19 9:38 ` Pieter Wenk
2000-01-16 17:53 ` Stainless Steel Rat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r9fiird3.fsf@serpent.local \
--to=lconrad@world.std.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).