https://bugzilla.novell.com/show_bug.cgi?id=419913
User nfbrown@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=419913#c6
Neil Brown
I also wonder why portmap doesn't try to stabilize port assignments a bit by reusing the previous port of a service.
There is a common misconception that portmap assigns port numbers. It does not. The RPC service provided chooses a port number and registers it with portmap. It has no way to find out what old port number might have been in use. I must admit that I don't much like the idea of having init.d/nfs restart the firewall. The code in init.d/network which does this looks rather fragile and I'd rather not duplicating and so increase the maintenance burden. If an admin is restarting nfs by hand, then restarting the firewall as well is a reasonable thing to expect I think. However if 'nfs' gets restarted as part of a software update, you would really like everything to 'just work'. Maybe restarting the firewall should be a standard 'last step' of a software installation, like running ldconfig. Another alternative would be to have e.g. /sbin/SuSEfirewall2 reload do all the checks that init.d/network currently does, and restarts the firewall if appropriate. Lugwig: What would you think of that last option? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.