Dan Weber
--- Begin Message ---What about kernel capabilities, cap_bind_service, and cap_set*id? They are a POSIX thing, so it should work everywhere dbmail does.Dan Weber Paul J Stevens wrote:This was discussed at length on the -devel list recently. The process running as root is not processing requests for clients. It's only purpose is (re)binding the port and forking off child processes that do the actual processing. This is how things are done. For example, apache uses this same approach.There are solutions that can remedy this, but none of those are portable AFAIK. Esp. kernel level capabilities come to mind.Bobby wrote:Hi all, I have configured my 1.2.7b with dbmail:dbmail. What I noticed is that the first process stays with root:root 1763 0.0 0.0 2008 556 ? S 03:37 0:00 /usr/local/sbin/dbmail-pop3d dbmail 1764 0.2 0.0 2056 652 ? S 03:37 0:00 /usr/local/sbin/dbmail-pop3d dbmail 1765 0.0 0.0 2056 748 ? S 03:37 0:00 /usr/local/sbin/dbmail-pop3d dbmail 1766 0.0 0.0 2056 748 ? S 03:37 0:00 /usr/local/sbin/dbmail-pop3d dbmail 1768 0.0 0.0 2056 748 ? S 03:37 0:00 /usr/local/sbin/dbmail-pop3dAny ideas? Best regards, Bobby [EMAIL PROTECTED] _______________________________________________ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
signature.asc
Description: OpenPGP digital signature_______________________________________________ Dbmail mailing list Dbmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
--- End Message ---
signature.asc
Description: OpenPGP digital signature