Digging further into the source code, there are a lot of arguments to mserver5 that are not settable by any means other than directly invoking the mserver5 executable. Some, such as --single-user aren't even in the man pages, at least not the man pages
I have.
Given that monetdbd seems to be the preferred method for invoking and controlling mserver5 processes, why are so many arguments to mserver5 not manageable via the combination of monetdbd and monetdb properties?
Alex,
Thanks for the suggestion. I ended up adding a dbextra property to databases so that we can use the same mechanism of "monetdb set dbextra=…." to control.
It was a pretty simple patch. If you compile the source, I'd be happy to get it to you.
Thanks,
Vince
Hi,
I use wrapper shell in such case. May be useful for you.
$ mv /usr/bin/mserver5 /usr/bin/mserver5.bin
$ vim /usr/bin/mserver5
#!/usr/bin/env bash
exec /usr/bin/mserver5.bin --set gdk_vmtrim yes --set gdk_vm_maxsize 200000000000 --dbextra=/mnt/data/monetdb/extra $@
Alexey Manaev,
Head of software development
CJSC "RUTUBE"
The information transmitted, including any attachments, is intended only for the individual or entity to which it is addressed, and may contain confidential and/or privileged information. Any review, retransmission, dissemination or other use of, or taking
of any action in reliance upon, this information by individuals or entities other than the intended recipient is prohibited, and all liability arising therefrom is disclaimed. If you have received this communication in error, please delete the information
from any computer and notify the sender.