Hi,
I've updated my patch according to all comments received:
Please review and test before it hits the tree.
http://home.selasky.org:8192/sysctl_tunable.diff
--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
On 06/18/14 23:13, John Baldwin wrote:
On Wednesday, June 18, 2014 4:36:24 pm Hans Petter Selasky wrote:
On 06/18/14 15:44, John Baldwin wrote:
On Wednesday, June 18, 2014 7:36:53 am Hans Petter Selasky wrote:
Hi,
I'll probably put it into the tree next week.
I think having CTLFLAG_TUN d
On Wednesday, June 18, 2014 4:36:24 pm Hans Petter Selasky wrote:
> On 06/18/14 15:44, John Baldwin wrote:
> > On Wednesday, June 18, 2014 7:36:53 am Hans Petter Selasky wrote:
> >> Hi,
> >>
> >> Sometimes sysctl's default value needs to be setup at boot time and not
> >> when the rc.d/sysctl is ru
On 06/18/14 15:44, John Baldwin wrote:
On Wednesday, June 18, 2014 7:36:53 am Hans Petter Selasky wrote:
Hi,
Sometimes sysctl's default value needs to be setup at boot time and not
when the rc.d/sysctl is running. Currently this is done by having two
statements in the kernel:
TUNABLE_INT("net.
On Wednesday, June 18, 2014 7:36:53 am Hans Petter Selasky wrote:
> Hi,
>
> Sometimes sysctl's default value needs to be setup at boot time and not
> when the rc.d/sysctl is running. Currently this is done by having two
> statements in the kernel:
>
> TUNABLE_INT("net.graph.mppe.log_max_rekey",
Hi,
Sometimes sysctl's default value needs to be setup at boot time and not
when the rc.d/sysctl is running. Currently this is done by having two
statements in the kernel:
TUNABLE_INT("net.graph.mppe.log_max_rekey", &mppe_log_max_rekey);
SYSCTL_INT(_net_graph_mppe, OID_AUTO, log_max_rekey, CT
