Thanks. On 12/13/2011 10:38 AM, Fabian Groffen wrote:
Just answering the bit I have an answer for immediately.
On 13-12-2011 10:06:00 -0700, Joseph Brower wrote:
Another concern is that in our installation, we don't see a MonetDB.conf file. I was hoping that we could specify how much RAM we'd like to allow MonetDB to consume. This is to ensure that our memory manager doesn't kill MonetDB, since that's the primary role of this server. Is this a file that we should create? I'm still fairly new to MonetDB and as a result, am still trying to find my way with it. Short answer, you can't. The config files are gone too, infavour of settings managed by monetdbd. Is there any documentation about how to properly manage settings via monetdbd? The last concern I have is the log file size. Is there a way (once we've ironed out the before mentioned issues) to instruct MonetDB to only log things of a certain importance or higher? For example, to only log ERR rather than ERR and MSG messages? Our log files will become quite large and unmanageable if we don't disable or implement some sort of log rotation system. There is no notion of a log-level, and MSG and ERR messages can't be separated either. You could locally patch, but I don't think it's worth it. Rotating logs is fairly easy. monetdbd accepts SIGHUP to reopen its logfile, so it's easy to integrate with logrotate.
That's what I figured. :-D I'll make sure we implement the log rotation. I've done some more research. It appears to be an issue with how our other system is inserting information. We'll be continuing to diagnose this. Thanks, Joseph Brower