Igor Podlesny writes: > On Sat, 27 Apr 2019 at 12:26, Sebastien Marie <sema...@online.fr> wrote: > > On Sat, Apr 27, 2019 at 12:17:21PM +0700, Igor Podlesny wrote: > > > Previously users could have different behaviour of malloc simultaneously: > one in > > > global FS, others in chroots. Say, in global it could be more relaxed > [...] > > malloc(3) man page mentions several ways to set malloc options: > > > > - globally with vm.malloc_conf sysctl(2) > > - externally per apps with environment variable MALLOC_OPTIONS > > - internally per apps with global variable malloc_options in the program > > > > So I suppose you want to look at exported MALLOC_OPTIONS environment > > variable. > > Wrong. Environment is easy to be changed by any non-privileged process. > OTOH, root owned /etc/malloc.conf is not.
Back then, when both /etc/malloc.conf and MALLOC_OPTIONS were set, which did a program prefer? -- Anthony J. Bentley
