Hello Matthias,

hm, the systctls are present on my 64 bit testing machine:

[root@maverick ~]# sysctl -p

• snip -

vm.mmap_rnd_bits = 32 vm.mmap_rnd_compat_bits = 16

• snip -

[root@maverick ~]# arch x86_64

Unfortunately I do not have 32 bit hardware at hand, and the absence of those parameters surprises me.

@All: Does anybody have access to something more uncommon like ARM SOCs? What about those?

@All, second: Does it make sense to ship different sysctl values for different platforms?

Sorry for the inconvenience.

Thanks, and best regards, Peter Müller

Hi,

sorry, next one:

Commit https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=ef21f3e49d2998eb4a22...

"Changed sysctl values are:

vm.mmap_rnd_bits = 32 (default: 28) vm.mmap_rnd_compat_bits = 16 (default: 8)"

After 'sysctl -p' I get:

***SNIP*** ... error: "Invalid argument" setting key "vm.mmap_rnd_bits" error: "vm.mmap_rnd_compat_bits" is an unknown key ... ***SNAP***

Tested on Core 134/32bit, fresh install.

Can anyone confirm?

Best, Matthias