[Bug 227888] random port selection for daemons causes other daemons to fail

2025-01-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #7 from Martin Birgmeier --- Thank you for the suggestion for mountd, I should have thought of this myself. Maybe there are similar solutions to the other issues I regularly encounter. -- Martin -- You are receiving this mail

[Bug 227888] random port selection for daemons causes other daemons to fail

2025-01-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #6 from Rick Macklem --- You can use the "-p" command line option to mountd to tell it to use a specific port#. I think this should avoid the problem. Unfortunately the Sun Mount protocol was not assigned a port#, since Sun di

[Bug 227888] random port selection for daemons causes other daemons to fail

2025-01-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #5 from Martin Birgmeier --- Today: rsync (to be started via inetd) blocked by mountd: [0]# lsof | grep rsync mountd1137 root7u IPv60xf800489238c00 UDP *:rsync mountd1137 root

[Bug 227888] random port selection for daemons causes other daemons to fail

2025-01-18 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #4 from Martin Birgmeier --- Example of ypbind using the imap port, thereby blocking dovecot from starting: [0]# lsof | grep imap ypbind1457 root5u IPv40xf8006d392000 0 TCP *:imaps->*:* (LI

[Bug 227888] random port selection for daemons causes other daemons to fail

2025-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 Alexander Ziaee changed: What|Removed |Added Status|New |Open -- You are receiving this

[Bug 227888] random port selection for daemons causes other daemons to fail

2025-01-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #3 from Martin Birgmeier --- This is still a big issue with stable/14. Sometimes a freshly booted machine must be rebooted just because some daemon has hijacked a port which is required by another. This is especially bad if som

[Bug 227888] random port selection for daemons causes other daemons to fail

2020-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #2 from Andriy Gapon --- Unfortunately, RPC does not have default ports. They are picked up from a special range. It's been this way forever, AFAIK. One "solution" is to request a fixed port for each RPC-based service if a serv

[Bug 227888] random port selection for daemons causes other daemons to fail

2020-05-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 --- Comment #1 from Martin Birgmeier --- This behavior is still a problem in 12.1 - every so often inetd cannot start some service, or some other service cannot start (for example dovecot) because its port is already used, for example by rp

[Bug 227888] random port selection for daemons causes other daemons to fail

2018-05-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227888 Mark Linimon changed: What|Removed |Added Component|standards |conf Keywords|