From: "Charles philip Chan" <cpchan@sympatico.ca>
Subject: Re: fetchmail as cronjob + gnus -- safe?
Date: Wed, 17 Aug 2005 15:42:52 -0400 [thread overview]
Message-ID: <87d5oce4eb.fsf@MagnumOpus.local> (raw)
In-Reply-To: <87fyt8skhg.fsf@wilson.rwth-aachen.de>
[-- Attachment #1: Type: text/plain, Size: 468 bytes --]
On 17 Aug 2005, bronger@physik.rwth-aachen.de wrote:
> Theoretically it is possible that both actions happen at the same
> time. Is this dangerous, or is some locking mechanism used to do it
> safely?
I have been doing this for many years with no problems at all. After all
this is what fetchmail was designed for.
Charles
--
"Linux: the operating system with a CLUE...
Command Line User Environment".
(seen in a posting in comp.software.testing)
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2005-08-17 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-17 14:31 Torsten Bronger
2005-08-17 19:42 ` Charles philip Chan [this message]
2005-08-17 20:21 ` Torsten Bronger
2005-08-18 2:19 ` Johan Bockgård
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=87d5oce4eb.fsf@MagnumOpus.local \
--to=cpchan@sympatico.ca \
/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).