question on new MV 3.14 database handling

[Kyle Hayes <kyle540@quicknet.net>]

I am trying to use the new MV 3.14 database handling.  According to Mike's
notes in the announcement, you can add Database entries to minivend.cfg
and they will be available globally and will only be opened once.  Great.

How do I do this?

I took the Database entries from catalog.cfg and put them into
minivend.cfg.  I had to remove all the NoImport statements which is not
good because now I am worried that MV will do something with a database
that I don't want.  Most of my databases are SQL.  When I restart MV, I
get:

[minivend@www2 minivend]$ ./bin/restart_unix Sent TERM to server on PID
7777. MiniVend server stopped. MiniVend V3.14 _mv_admin config error:
import_database: No database name!
 
 
_mv_admin: error in configuration. Skipping. _mv_admin: config error.
Skipping.

Configuring catalog reseller...Bad shipping file for zone 'u',
lookup disabled. reseller config error: import_database: No database name!
 
 
reseller: error in configuration. Skipping. reseller: config error.
Skipping.
MiniVend server started in UNIX mode(s) (process id 7788)

And of course, I have exactly zero catalogs available now.

The error log has less information than that above.  When the databases
are in the catalog.cfg file, everything is quite happy and horribly slow.
I am trying to cut down on my overhead cost by keeping the databases open.

I am using MV 3.14, Red Hat Linux 6.0, MySQL 3.22.25, Perl 5.005x.

I am trying to move _all_ of my databases to the global minivend.cfg file.
Products, etc.

Best,
Kyle