
On 21-02-2008 14:55:10 +0100, Michael Schmidt wrote:
Hi Fabian,
As far as I can see, the fixes from stable have not yet been propagated to the current (HEAD) branch yet. In that respect I am sorry to tell you that you still have to wait for it.
you're right, I've installed the latest nightly build and the -w option is not yet supported. But don't worry, I'll try again in the coming days.
The fixes have just been merged into the curent branch, so either use CVS, or check tomorrow's nightlies for the "current" branch.
Niels thinks that the crashes are due to the sql_logs not being thrown away. Could you check if the var/MonetDB5/sql_logs/DBNAME is removed by monetdb destroy -f as well as var/MonetDB5/dbfarm/DBNAME?
Great, this solves my problem. I simply extended my script by
rm -Rf .../sql_logs/DBNAME
just after destroying the database, and everything works fine now. You were right that this log file is not removed by the destroy command (FYI: the dbfarm subfolder is removed correctly).
Please let me know when you have fixed this bug, then I will remove the rm -Rf again, and can of course test for you whether everything still is fine.
Could you file a bug for this issue with monetdb?