From: Stroller <stroller@stellar.eclipse.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fcron & fetchmail & procmail and the "why not?"
Date: Tue, 22 Sep 2009 12:46:27 +0100 [thread overview]
Message-ID: <F99C3104-C06E-4D38-A0DE-EEC692247812@stellar.eclipse.co.uk> (raw)
In-Reply-To: <20090921160604.GC5876@solfire>
On 21 Sep 2009, at 17:06, meino.cramer@gmx.de wrote:
> ...
> To not to involve stdout was the hack!
>
> Currently I am running fetchmail via fcron and does what it should
> since fetchmail directly reports to /dev/null.
Sorry to seem like a numptie, but are you saying you fixed it?
The problem was solved merely by adding the redirect?
> I think I will change the whole suff to run in daemon mode, since I
> think (to be read as: "...not know for sure...") that it is a little
> bit more performant. Or?
I run as user, 2 users, each with their own .fetchmailrc & each
adding their own entry into their own crontab. I.E. just like you have
it now. I have been running my system this way for years.
The notion of daemon mode bothers me, because it must be run by root
(IIRC) and the various users all put their separate private email
passwords in a single file in /etc OTOH, the daemon mode
configuration file is readable only by root, and if the root account
is compromised then the users' private .fetchmailrc files can be read
anywhere.
Fetchmail is a bit of a kludge, really. I wouldn't worry too much
about being best conformant.
Stroller.
next prev parent reply other threads:[~2009-09-22 11:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 15:34 [gentoo-user] fcron & fetchmail & procmail and the "why not?" meino.cramer
2009-09-20 18:21 ` Ward Poelmans
2009-09-21 2:05 ` [gentoo-user] " Harry Putnam
2009-09-21 2:29 ` meino.cramer
2009-09-21 6:39 ` Johám-Luís Miguéns Vila
2009-09-21 15:43 ` meino.cramer
2009-09-21 15:46 ` Ward Poelmans
2009-09-21 13:02 ` [gentoo-user] " Stroller
2009-09-21 16:06 ` meino.cramer
2009-09-22 11:46 ` Stroller [this message]
2009-09-22 13:16 ` Neil Bothwick
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=F99C3104-C06E-4D38-A0DE-EEC692247812@stellar.eclipse.co.uk \
--to=stroller@stellar.eclipse.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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