From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] fcron & fetchmail & procmail and the "why not?"
Date: Mon, 21 Sep 2009 18:06:04 +0200 [thread overview]
Message-ID: <20090921160604.GC5876@solfire> (raw)
In-Reply-To: <BFACEEA8-E2D8-4DCD-83D7-DDF71BFEE2FF@stellar.eclipse.co.uk>
Stroller <stroller@stellar.eclipse.co.uk> [09-09-21 17:13]:
>
> On 20 Sep 2009, at 16:34, meino.cramer@gmx.de wrote:
> >...
> >When using the line:
> >
> > @ 5 fetchmail -a
> >
> >nothing happens: The mail remains on the server and can be downloaded
> >with
> >
> > fetchmail -a
> >
> >from the commandline.
>
> Here my crontab says:
>
> 0-59/4 * * * * /usr/bin/fetchmail > /dev/null 2>&1
>
> I suggest trying the full path, but you may also be able to redirect
> to somewhere other than /dev/null & perhaps see something useful?
>
> Stroller.
>
Ha! :)
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.
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?
Thanks for the help! :)
Keep hacking!
mcc
--
Please don't send me any Word- or Powerpoint-Attachments
unless it's absolutely neccessary. - Send simply Text.
See http://www.gnu.org/philosophy/no-word-attachments.html
In a world without fences and walls nobody needs gates and windows.
next prev parent reply other threads:[~2009-09-21 16:06 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 [this message]
2009-09-22 11:46 ` Stroller
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=20090921160604.GC5876@solfire \
--to=meino.cramer@gmx.de \
--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