Hello,
There are two copies of the webinator database, db1 and db2. This makes sense because the webinator creates an entire new database for a new walk and then activates the new database once the walk is done and gets rid of the old one. The old database is available while the walk is in progress.
But sometimes I see both db1 and db2 after a walk. Sometimes I see them after a refresh walk. It doesn't make as much sense to me to create a new database during a refresh walk since you're should be updating the links in the existing database.
Is this a problem? If so, how can I figure out why it is happening and how to prevent it?
Thanks, John
There are two copies of the webinator database, db1 and db2. This makes sense because the webinator creates an entire new database for a new walk and then activates the new database once the walk is done and gets rid of the old one. The old database is available while the walk is in progress.
But sometimes I see both db1 and db2 after a walk. Sometimes I see them after a refresh walk. It doesn't make as much sense to me to create a new database during a refresh walk since you're should be updating the links in the existing database.
Is this a problem? If so, how can I figure out why it is happening and how to prevent it?
Thanks, John
