Probably you aren't but the binpkgs you use are. You'll probably have less frustrations at this point if you just compile from source, using the monetdb-install.sh script. What seems wrong here is that the default path is set to the builddir instead of the target dir.
Thanks for the suggestion. My results were mixed. The good news is that in the latest nightly stable build the problems with the intermitant bad passwords and with the server failing to reboot have been fixed! So that is great! However the not-so-good news is that now my JDBC connection is no longer working properly. Do I need to use a newer version of the JDBC driver in conjunction with this latest stable nightly build? If so I could not find it - where do I get it? The problem with the JDBC driver is that when running with merovingian I get: Maximum number of redirects reached, aborting connection attempt. Sorry. then instead of running withmerovingian, as a test I ran with: mserver5 --dbinit="include sql;" and when running that way I get InvalidCredentialsException:checkCredentials:Invalid credentials for user 'monetdb' However I am using the default username and password of monetdb for both and haven't changed this. Furthermore If I run mclient with -umonetdb and specify monetdb as the password it accepts it there just fine. So I assume monetdb is still the default valid username/password for this stable nightly. But for some reason when I pass this as the user name and password in my JDBC connection it won't accept it. As mentioned earlier, this part was working just fine under the released version of MonetDB5. Can someone please help? I am running out of time to get this implemented so I am hoping to close this loop today. Thank you so much!!