From: Pieter Wenk <pwenk@urbanet.ch>
Subject: Re: What is the use of /var/lock/news
Date: Sun, 16 Jan 2000 20:29:10 +0100 [thread overview]
Message-ID: <20000116202910.A3507@sre-4-139.urbanet.ch> (raw)
In-Reply-To: <vafbt6mmfwa.fsf@lucy.cs.uni-dortmund.de>
On dim, 16 jan 2000, Kai Großjohann wrote:
>Pieter Wenk <pwenk@urbanet.ch> writes:
>
>> [...] But why leafnode's NNTP server is creating this
>> file ? I understand this protective measure. But for what
>> reason leafnode is locking ?[...]
>
>It is important that the _first_ instance of Leafnode does the
>locking. This way, Leafnode can check for the existence of a lock
>file, and barf if it exists.
Kai, the problem with these files is the following.
You are under ~/user, fire gnus...
Know with an existing lock file...fetching will not
work correctly and you might notice this only too
late....
Leafnode resp. fetchnews has certainly reasons to
create such a file...but I sincerely would appreciate
that Cornelius could find another way....
Like this..IMHO it's not a satisafoctory solution.
Now what are you suggesting I have to do ??
Regards to Dortmund
--
/ / (_)____ __ ____ __
Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland
/____/_/_//_/\_,_/ /_/\_\
next prev parent reply other threads:[~2000-01-16 19:29 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
2000-01-16 9:43 ` Pieter Wenk
2000-01-16 11:09 ` Kai Großjohann
2000-01-16 19:29 ` Pieter Wenk [this message]
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=20000116202910.A3507@sre-4-139.urbanet.ch \
--to=pwenk@urbanet.ch \
/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).