Charlie Brady wrote:
That's an added complication, and more code - which usually means that
more things can go wrong. In what circumstances would someone want more
than one interface, but not all interfaces?
I was wondering about this myself and then I thought that someone might
want to run smtpd on 127.0.0.1 (for local [trusted] applications) and
have two other interfaces (say external and internal on a multihomed
host). Using a firewall to limit access is not helpful in this case.
There is some utility to having something between all and one.
As long as the performance is [largely] unaffected, the code isn't that
complicated (and will probably go away when high_perf is merged in any
case), so I think we should commit it...
John
- Re: PATCH: let forkserver listen on multiple interfaces John Peacock
-
