Hello, I like to ask if postfix/master process can simply behave like a supervisor to keep a non postfix process simply up and running. It should start a process and if the process exit for any reason, it should be restarted after a short delay (optional: some logging)
My use-case is a postfix instance running in a container. postfix is started with "start-fg" and master has PID 1 STDIN is /dev/null, STDOUT+STDERR may be /dev/null, handled by postlog or the process write to container's /dev/stdout https://www.postfix.org/master.5.html clearly say, such mode is not possible today. So it would be like a feature request. It mention spawn for that job. But spawn has limitations not fitting for a process like postfix-tlspol [1] Why not use a separate container? My postfix-container have dedicated, fixed ip addresses. Using separate container would require additional ip addresses or data will flow different then connections initiated by the postfix-container itself. (sounds scary, local limitations ...) Does that make sense? Do I oversee an other possibility? Andreas [1] https://github.com/Zuplu/postfix-tlspol _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
