On 2020-05-11 21:45, Robert Moskowitz wrote: > > > On 5/11/20 9:28 AM, Ed Greshko wrote: >> On 2020-05-11 20:39, Robert Moskowitz wrote: >>> And now you are paying the memory, cpu, etc. cost of having postfix running >> Oh, well, I suppose I've never seen an idle postfix take up any noticeable CPU time or memory >> on any of my systems. > > How can it not take up memory? It may be swapped out, but there should be something there watching port 25, at least. It is rather tiny. Taking up 0.7% of memory in a VM with 1.2G assigned to it. > > It does seem to be event triggered, like a connection to port 25 or whatever other ports it is configured for. So it would be idling for the post part. But then when you use it for a simple MDA action, is it written modularly so you only load what is needed? > > Yeah, not too bad. But to configure postfix for only this function and to protect against any misuse, is yet something else to do. Misuse? Listening only on 127.0.0.1 by default so only users on the machine it is running can abuse it. :-) > > Plus writing my own script has been fun and educational! ;) Sounds like lots of fun. > > The problem is with cron. I am going to have to drop a note to Vixie; it has been a couple years since the two of us have had fun sparing... really he is a great guy, and I learned a lot from him working on IETF mail and dns workgroups. > Well, since cronie is a fork of vixie-cron he may not have much insight. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
