default DB logs rewalk to itself, not to temp DB

Post Reply
User avatar
Thunderstone
Site Admin
Posts: 2504
Joined: Wed Jun 07, 2000 6:20 pm

default DB logs rewalk to itself, not to temp DB

Post by Thunderstone »



For half a dozen rewalks (launched via cron job) gw created temporary
database _db but gw.log entries for each rewalk appeared in gw.log file in
main db directory.

gw.log files created in each temp db directory (named _db, __db, etc.) only
showed creation of temp db.

I had wiped and walked anew default db. That was interrupted for unknown
reason, so I walked again and it correctly identified URLs already in the
database, walking the rest.

I had also set two scheduled rewalks of two other databases using "nohup
[command] &" format suggested in previous message. They succeeded without a
hitch.

Can I delete main db directory and invoke gw -d- -create to start afresh?

Is there a secret to wiping and walking -d- ?

Monty Kersell



User avatar
Thunderstone
Site Admin
Posts: 2504
Joined: Wed Jun 07, 2000 6:20 pm

default DB logs rewalk to itself, not to temp DB

Post by Thunderstone »




The _db directory should not be present after a successful rewalk.
It's presence indicates some kind of problem. Check the output
from gw (cron will generally mail output of it's jobs to you).


Yes.


No.


Post Reply