> I failed to find a case where to use SYSCTL_INT_UNBOUNDED. We always > find better "common sense" limits than completely unconstrained.
I agree. There must always be a bound.
- Re: sysctl net.inet.ip.arpqueued read only Theo de Raadt
- Re: sysctl net.inet.ip.arpqueued read only Alexander Bluhm
- Re: sysctl net.inet.ip.arpqueued read only Vitaliy Makkoveev
- Re: sysctl net.inet.ip.arpqueued read only Greg Steuck
- Re: sysctl net.inet.ip.arpqueued read only Alexander Bluhm
- Re: sysctl net.inet.ip.arpqueued read only Vitaliy Makkoveev
- Re: sysctl net.inet.ip.arpqueued read only Greg Steuck
- Re: sysctl net.inet.ip.arpqueued read only Theo de Raadt
- Re: sysctl net.inet.ip.arpqueued read only Vitaliy Makkoveev
- Update the remaining SYSCTL_INT_READONLY cases Greg Steuck
- Re: Update the remaining SYSCTL_INT_READONLY cases Theo de Raadt
- Re: Update the remaining SYSCTL_INT_READONLY cases Vitaliy Makkoveev
- Re: Update the remaining SYSCTL_INT_READONLY cases Greg Steuck
- Re: Update the remaining SYSCTL_INT_READONLY cases Vitaliy Makkoveev
