Skip to content

Conversation

@josh4trunks
Copy link
Contributor

Update rtpproxy.in.freebsd in the upstream source.
This will allow the removable of 'files/patch-scripts_rtpproxy.in.freebsd' in the FreeBSD port.

Update rtpproxy.in.freebsd in the upstream source. This will allow the removable of 'files/patch-scripts_rtpproxy.in.freebsd' in the FreeBSD port.
@josh4trunks
Copy link
Contributor Author

This is semi-related to the bug to update the FreeBSD port to version 3.1.1. Though neither patch / PR is dependent on the other.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283019

Regarding the FreeBSD bug, @sobomax can you explain if/why "AR=llvm-ar RANLIB=llvm-ranlib" is needed? Thank you

Add shutdown as recommended by 'Practical rc.d scripting in BSD'
@josh4trunks
Copy link
Contributor Author

josh4trunks commented Apr 30, 2025

The options currently provided are listed below; and I agree that this is a reasonable list

  • Control Socket
  • IPv4 Listen IP Address(es)
  • Advertised Address(es)
  • UID:GID to switch to

Any other options could be changed by setting 'rtpproxy_flags', for example

  • sysrc rtpproxy_flags="-m 10000 -M 20000"

@sobomax
Copy link
Member

sobomax commented May 8, 2025

@josh4trunks merged thanks for submission! ❤️ Please next time squash your commits and de-duplicate the comments before opening a PR. You can also do it later on, by force-pushing the update to your own repo (if you need to make some last-minute changes once PR is open).

@sobomax sobomax closed this May 8, 2025
@josh4trunks
Copy link
Contributor Author

@josh4trunks merged thanks for submission! ❤️ Please next time squash your commits and de-duplicate the comments before opening a PR. You can also do it later on, by force-pushing the update to your own repo (if you need to make some last-minute changes once PR is open).

Sounds good, ok I will try to do those steps next time!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants