Zhenqing Li <[EMAIL PROTECTED]> writes:
> You can modify your ~/.fetchmailrc and include these into the beginning:
>
> set daemon 60
>
> And start the fetchmail script in the initial boot time (put it into
> /etc/init.d )
>
Although I prefer to cron, but you teached me how to let a app run at
the
anhnmncb <[EMAIL PROTECTED]> writes:
> Bastien <[EMAIL PROTECTED]> writes:
>
>> Fetching them in the background with fetchmail doesn't force you to read
>> them. And if you don't use any fancy notification mechanism, fetching
>> them in the background will just make it faster for Gnus to fetch th
William Xu <[EMAIL PROTECTED]> writes:
> That i raise this question is because recently I'm playing with OS X's
> launchd daemon controller, which has a nice launch-on-demand feature.
> I'm not quite sure about which is better. OS X tends to like
> launch-on-demand.
Mac OS X's use of Launch-On
William Xu <[EMAIL PROTECTED]> writes:
>> This might be a personal opinion, but if a tool as a feature which
>> works, why use another tool to do the same thing? I think many Unix
>> authors would agree with this principe.
>
> That i raise this question is because recently I'm playing with OS X's
Damien Wyart <[EMAIL PROTECTED]> writes:
> * William Xu <[EMAIL PROTECTED]> in gnu.emacs.gnus:
>> Are there many differences between:
>
>> 1. fetchmail -d $interval
>> 2. a cron job running `fetchmail' every $interval
>
> Not really (except you will have to start and stop fetchmail each time,
> b
William Xu a écrit profondement:
| Are there many differences between:
|
1. fetchmail -d $interval // is a daemon
2. a cron job running `fetchmail' every $interval // loads a one time
fetchmail - but loads it every time the cronjob kicks in
--
SlackRat
-
Just remember: Government works o
* William Xu <[EMAIL PROTECTED]> in gnu.emacs.gnus:
> Are there many differences between:
> 1. fetchmail -d $interval
> 2. a cron job running `fetchmail' every $interval
Not really (except you will have to start and stop fetchmail each time,
but the costs are negligible of course) ; I just feel
Bastien <[EMAIL PROTECTED]> writes:
> William Xu <[EMAIL PROTECTED]> writes:
>
>> Are there many differences between:
>>
>> 1. fetchmail -d $interval
>> 2. a cron job running `fetchmail' every $interval
>
> Not in the result. But surely in the process. My guess is that running
> fetchmail as a
William Xu <[EMAIL PROTECTED]> writes:
> Are there many differences between:
>
> 1. fetchmail -d $interval
> 2. a cron job running `fetchmail' every $interval
Not in the result. But surely in the process. My guess is that running
fetchmail as a daemon is faster and less resource-consuming.
--
Damien Wyart <[EMAIL PROTECTED]> writes:
>> How to fetch them in the background? Do you mean I throw fetchmail
>> into crontab to let it run every some time?
>
> No, fetchmail is *designed* to be run in the background ; you just have
> to configure the default interval it will use between fetching
Bastien <[EMAIL PROTECTED]> writes:
> Add this into your ~/.fetchmailrc :
>
> set daemon 1000
>
> ... and yes, reading the fetchmail documentation will also help!
>
Thank you, I've got what you mean.
--
Regards,
anhnmncb
gpg key: 44A31344
___
info
anhnmncb <[EMAIL PROTECTED]> writes:
>>> Mails isn't like rss or news, I want to fetch them whenever I want to
>>> read them.
>>
>> But *why*?
>>
> If I don't fetch rss for a long time, say 7 days, It's likely I will
> miss many news. But for mail, I could get them without losing any of
> them.
anhnmncb <[EMAIL PROTECTED]> writes:
> Bastien <[EMAIL PROTECTED]> writes:
>
>> Fetching them in the background with fetchmail doesn't force you to read
>> them. And if you don't use any fancy notification mechanism, fetching
>> them in the background will just make it faster for Gnus to fetch th
* anhnmncb <[EMAIL PROTECTED]> in gnu.emacs.gnus:
> How to fetch them in the background? Do you mean I throw fetchmail
> into crontab to let it run every some time?
No, fetchmail is *designed* to be run in the background ; you just have
to configure the default interval it will use between fetchin
Bastien <[EMAIL PROTECTED]> writes:
> anhnmncb <[EMAIL PROTECTED]> writes:
>
>> Mails isn't like rss or news, I want to fetch them whenever I want to
>> read them.
>
> But *why*?
>
If I don't fetch rss for a long time, say 7 days, It's likely I will
miss many news. But for mail, I could get the
Bastien <[EMAIL PROTECTED]> writes:
> Fetching them in the background with fetchmail doesn't force you to read
> them. And if you don't use any fancy notification mechanism, fetching
> them in the background will just make it faster for Gnus to fetch them
> in /var/mai/anhmncb
>
How to fetch them
(Redirecting to the list, if you don't mind.)
anhnmncb <[EMAIL PROTECTED]> writes:
> Mails isn't like rss or news, I want to fetch them whenever I want to
> read them.
But *why*?
Fetching them in the background with fetchmail doesn't force you to read
them. And if you don't use any fancy n
anhnmncb <[EMAIL PROTECTED]> writes:
> Hi, list,
> I have these lines in .gnus
> (setq mail-sources
> '((file :path "/var/mail/anhnmncb"
> :prescript "fetchmail")))
> When gnus rechieves mail, the fetchmail's output doesn't show anywhere,
> I can't know what status it's in, how t
Hi, list,
I have these lines in .gnus
(setq mail-sources
'((file :path "/var/mail/anhnmncb"
:prescript "fetchmail")))
When gnus rechieves mail, the fetchmail's output doesn't show anywhere,
I can't know what status it's in, how to configure to let fetchmail's
output echo into mi
19 matches
Mail list logo
