From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: What is the use of /var/lock/news
Date: 16 Jan 2000 12:53:58 -0500 [thread overview]
Message-ID: <m3wvp9oqbt.fsf@peorth.rgo.gweep.net> (raw)
In-Reply-To: Pieter Wenk's message of "Sun, 16 Jan 2000 10:43:12 +0100"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* Pieter Wenk <pwenk@urbanet.ch> on Sun, 16 Jan 2000
| Thanks a lot. But why leafnode's NNTP server is creating this
| file ? I understand this protective measure. But for what
| reason leafnode is locking ? Is something wrong with leafnode ?
| I assume, leafnode is creating such a file for a reason?
| >Then I suspect leafnode's NNTP server is creating the lock files. They are
| >created to prevent two or more instances of leafnode or especially
| >fetchnews from being started, which would effectively destroy your spool.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4ggW2gl+vIlSVSNkRAubpAJ9RaogDzk7DvUF2PIcOoyaKP/5YMgCgoq6b
j/Ur/q708Hk/eQl1X3uW2DU=
=6WUJ
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ When not in use, Happy Fun Ball should be
Minion of Nathan - Nathan says Hi! \ returned to its special container and
PGP Key: at a key server near you! \ kept under refrigeration.
prev parent reply other threads:[~2000-01-16 17:53 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
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 [this message]
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=m3wvp9oqbt.fsf@peorth.rgo.gweep.net \
--to=ratinox@peorth.gweep.net \
/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).