Re: about the virtual address space of processes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Rene Herman wrote:
On 28-04-08 19:31, Scott Lovenberg wrote:

Rene Herman wrote:
Looking closer, the CONFIG option keeps non-heap address-space randomization enabled. What you want to have is:

$ cat /proc/sys/kernel/randomize_va_space
0

Set it, as root, via

# echo -n 0 >/proc/sys/kernel/randomize_va_space

Off topic, but do you need the -n flag? I always just "echo num > /proc/sys/path" and I've never had a problem, but is there a case where it matters?

No you don't in fact need it for sysctls -- the first newline is simply ignored (as is all other trailing whitespace by the way).

When you echo things into /sys (a device id into a driver "bind" attribute for example) that's not always the case though and my "-n" came about sort of automatically.

The "proper" way of setting sysctl's is in fact though the sysctl program:

# sysctl kernel.randomize_va_space=0

but hey...

Rene.
Actually, I think sysctl is deprecated and on its way out. I'd better double check that. I think the general consensus was that there was no need for it since you can just echo in arguments. Maybe Red Hat is deprecating it and I'm thinking it's everyone. I'll get back to you guys on this in a few hours.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux