Praedor Atrebates grabbed a keyboard and wrote:
>
> Thanks for the reply but the problem was:
>
> I had a ~/.fetchmailrc. It worked so long as I started fetchmail myself.
> If I tried to start fetchmail thus (as root) "/etc/init.d/fetchmail start"
> or if I started up MCC and then tried to start fetchmail from xservices I
> got the same result: failure. In my logs I would get a message that
> there was no mailserver specified. I DID have a mailserver specified in
> my .fetchmailrc. I then opened up webmin and saw my personal fetchmail
> entry there yet fetchmail service would not start for "lack" of a
> mailserver to poll.
>
> Only after I copied my personal .fetchmailrc to /etc/fetchmailrc could I
> start fetchmail as a daemon in xservices and have it run properly at each
> startup. It didn't seem to care at all that I actually did have a valid
> ~/.fetchmailrc file and that it did contain a valid mailserver. This is
> why I asked the original question about how to get /etc/fetchmailrc setup
> instead of ~/.fetchmailrc (the latter wasn't working).
>
> - From your reply, I assume I should never have received the error I
> received - that fetchmail should have started up as a daemon without
> problem and simply used my personal .fetchmailrc. But it didn't.
Ok, my goof. That's what I get for trying to help when I've just woken
up. :-)
Bryon posted a message about how to point your fetchmail daemon to the rc
file of your choice, you can use that. Or as I mentioned, you can start
it from a cron job that runs every 5 minutes to have it poll your server
that often. Since it would be running as you, it would be no different
than if you started it yourself from a shell prompt.
--Dave
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
