I'm unclear why you're attempting external connections with an embedded server but it's for the vault issue at least it's trivial to avoid the dependency on an external file, e.g. in embeddedclient.c unlock the vault like this:
char* secret = (char*)"somehardcodedstring";
if (AUTHunlockVault(&secret) != MAL_SUCCEED)
return 0;

On Mon, Jan 4, 2010 at 3:23 PM, Guillaume Yziquel <guillaume.yziquel@citycable.ch> wrote:
Fabian Groffen a écrit :
> On 04-01-2010 21:02:16 +0100, Guillaume Yziquel wrote:
>> Hi.
>>
>> I've been creating a database from a call to monetdb_sql() from
>> libembeddedsql5.so, from my OCaml binding.
>>
>> After that, I start up a merovingian process and I do the following:
>>
>>> yziquel@seldon:~/git/ocaml-monetdb5$ monetdb status
>>>      name        state     uptime       health       last crash
>>> testdb          stopped               100%, 49s  -
>>> yziquel@seldon:~/git/ocaml-monetdb5$ monetdb start testdb
>>> starting database 'testdb'... FAILED
>>> start: starting 'testdb' failed: cannot start database 'testdb': no .vaultkey found (did you create the database with `monetdb create testdb`?)
>>
>> I'm quite baffled by the error I just got. What is this .vaultkey problem?
>
> Merovingian(1) and monetdb(1) enable increased security features of
> mserver5.  If you start mserver5 manually, you do not enable this.
>
> In short, you mix the usage of merovingian(1) and mserver5, that's
> asking for problems.

I'm not mixing the use of merovingian and mserver5, but mixing the use
of merovingian and monetdb_sql(). Or maybe I misunderstood you.

> If you want to create databases with merovingian(1), you best make a
> connection to merovingian(1)'s control channel to tell it to create a
> database.

OK. So is it possible to create a database via a call to monetdb_sql(),
and to access it via a command line tool such as mclient? If yes, how?

All the best,

--
     Guillaume Yziquel
http://yziquel.homelinux.org/

------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
MonetDB-users mailing list
MonetDB-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/monetdb-users