-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/22/07 17:26, Jochen Schulz wrote: > Ron Johnson: >> On 03/22/07 09:39, Jochen Schulz wrote: >>> If your /etc/fetchmailrc is empty anyway, you can edit >>> /etc/default/fetchmail to disable the system-wide fetchmail daemon >>> altogether. This solution has the advantage, that every user can manage >>> his/her own POP accounts (without the admin knowing their passwords), >>> but the disadvantage is that you have a fetchmail process for every >>> user. >> Are you talking about having a fetchmail daemon for *each* user? > > Yes.
That's... odd. (Not wrong, just odd.) > On most peoples' systems there's only a fistful of anyway. Not knowing that other people also run fetchmail from cron, I also configured fetchmail it to run from cron for each of 3 users on my system. Why created multiple daemons for activity that's going to run every X number of minutes, when cron is already specialized for that purpose? > > J. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGAyZBS9HxQb37XmcRAv2dAJ9ajPba0Psunlgyof2kCaM32KAkBACg4kCm yCK+zRPDn3wXJv1pK5TBiyY= =NpX6 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]