move parm order around in gb.conf

This commit is contained in:
Matt Wells
2014-06-16 06:07:11 -07:00
parent 9244e172d0
commit 3c1f89e052

102
gb.conf

@ -215,6 +215,57 @@
<dns14>0.0.0.0</>
<dns15>0.0.0.0</>
# If enabled, gigablast will repair the rdbs as specified by the parameters
# below. When a particular collection is in repair mode, it can not spider or
# merge titledb files.
<repairModeEnabled>0</>
# Comma or space separated list of the collections to repair or rebuild.
<collectionsToRepairOrRebuild><![CDATA[main]]></>
# In bytes.
<memoryToUseForRepair>300000000</>
# Maximum number of outstanding inject spiders for repair.
<maxRepairSpiders>32</>
# If enabled, gigablast will reinject the content of all title recs into a
# secondary rdb system. That will the primary rdb system when complete.
<fullRebuild>0</>
# If enabled, gigablast will keep the new spiderdb records when doing the full
# rebuild or the spiderdb rebuild.
<keepNewSpiderdbRecs>1</>
# If enabled, gigablast will recycle the link info when rebuilding titledb.
<recycleLinkInfo>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildTitledb>1</>
# If enabled, gigablast will rebuild this rdb
<rebuildPosdb>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildClusterdb>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildSpiderdb>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildLinkdb>0</>
# If disabled, gigablast will skip root urls.
<rebuildRootUrls>1</>
# If disabled, gigablast will skip non-root urls.
<rebuildNonrootUrls>1</>
# When rebuilding spiderdb and scanning it for new spiderdb records, should a
# tagdb lookup be performed? Runs much much faster without it. Will also keep
# the original doc quality and spider priority in tact.
<skipTagdbLookup>0</>
# add Ips here to bar them from accessing this gigablast server.
<banIps><![CDATA[]]></>
@ -329,54 +380,3 @@
# Log reminders to the programmer. You do not need this.
<logReminderMessages>0</>
# If enabled, gigablast will repair the rdbs as specified by the parameters
# below. When a particular collection is in repair mode, it can not spider or
# merge titledb files.
<repairModeEnabled>0</>
# Comma or space separated list of the collections to repair or rebuild.
<collectionsToRepairOrRebuild><![CDATA[main]]></>
# In bytes.
<memoryToUseForRepair>300000000</>
# Maximum number of outstanding inject spiders for repair.
<maxRepairSpiders>32</>
# If enabled, gigablast will reinject the content of all title recs into a
# secondary rdb system. That will the primary rdb system when complete.
<fullRebuild>0</>
# If enabled, gigablast will keep the new spiderdb records when doing the full
# rebuild or the spiderdb rebuild.
<keepNewSpiderdbRecs>1</>
# If enabled, gigablast will recycle the link info when rebuilding titledb.
<recycleLinkInfo>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildTitledb>1</>
# If enabled, gigablast will rebuild this rdb
<rebuildPosdb>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildClusterdb>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildSpiderdb>0</>
# If enabled, gigablast will rebuild this rdb
<rebuildLinkdb>0</>
# If disabled, gigablast will skip root urls.
<rebuildRootUrls>1</>
# If disabled, gigablast will skip non-root urls.
<rebuildNonrootUrls>1</>
# When rebuilding spiderdb and scanning it for new spiderdb records, should a
# tagdb lookup be performed? Runs much much faster without it. Will also keep
# the original doc quality and spider priority in tact.
<skipTagdbLookup>0</>