* Marc Lehmann: > after upgrading to 4.6, this apparently changed. wether caused by an > upgraded 4.5 database or simply because the 4.6 utilities don't work > anymore (or don't happen to work by chance) with environments configured > with set_thread_count (the documentation for that method says a process > might not be able to join such an enviornment unless it also cofigured an > is_alive function, which never happened in our case). > > the documentation is not clear wether a segfault is expected (the hint > that one should call DB_ENV->failchk before calling the utility seems to > indicate that they should work).
I think the idea is to call DB_ENV->failchk so that the other programs do not need to attempt recovery on their own. Have you tried specifying the right value of set_thread_count in the DB_CONFIG file? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
