| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| util:smbutil [2018/03/01 12:11] – Links to util:binkit changed to module:binkit digital man | util:smbutil [2018/03/01 12:20] – old revision restored digital man |
|---|
| The ''m'' command (for //maintenance//) instructs smbutil to mark old messages, and messages over the maximum sub-board limit, as //deleted// so that the disk space used by these message can be allocated to new messages. If you are using the 'Hyper Allocation' or 'Fast Allocation' method for your message bases, you must also use this utility to pack your message bases periodically. The pack (''p'') command instructs smbutilto compress the message bases, removing any unused allocation blocks (for messages marked as //deleted//). | The ''m'' command (for //maintenance//) instructs smbutil to mark old messages, and messages over the maximum sub-board limit, as //deleted// so that the disk space used by these message can be allocated to new messages. If you are using the 'Hyper Allocation' or 'Fast Allocation' method for your message bases, you must also use this utility to pack your message bases periodically. The pack (''p'') command instructs smbutilto compress the message bases, removing any unused allocation blocks (for messages marked as //deleted//). |
| |
| smbutil maintenance and/or packing should be done using an //exclusive// daily timed event (configured in [[module:binkit]]->External Programs->Timed Events). If your message bases are using the 'Fast Allocation' or 'Hyper Allocation' storage methods, you should run maintenance before packing (there is no reason to pack if you do not run maintenance!). If your message bases are configured for the 'Self Packing' method, you do NOT need to use smbutil to pack, only to perform maintenance. | smbutil maintenance and/or packing should be done using an //exclusive// daily timed event (configured in [[util:SCFG]]->External Programs->Timed Events). If your message bases are using the 'Fast Allocation' or 'Hyper Allocation' storage methods, you should run maintenance before packing (there is no reason to pack if you do not run maintenance!). If your message bases are configured for the 'Self Packing' method, you do NOT need to use smbutil to pack, only to perform maintenance. |
| |
| **Note**: | **Note**: |
| === Repair === | === Repair === |
| |
| If you have a message base that is severely corrupted (e.g. ''[[module:binkit]]'' cannot open it for index repair), you can use the following smbutil command-line to re-initialize the message base status header: | If you have a message base that is severely corrupted (e.g. ''[[util:fixsmb]]'' cannot open it for index repair), you can use the following smbutil command-line to re-initialize the message base status header: |
| |
| smbutil -C Rcs /sbbs/data/subs/badbase | smbutil -C Rcs /sbbs/data/subs/badbase |
| -display the status header | -display the status header |
| | |
| After repairing a message base in this manner, you may still need to run ''[[module:binkit]]'' on it to resolve any remaining errors reported by ''[[module:binkit]]''. | After repairing a message base in this manner, you may still need to run ''[[util:fixsmb]]'' on it to resolve any remaining errors reported by ''[[util:chksmb]]''. |
| |
| === Auto-post === | === Auto-post === |
| | |
| **Note**: | **Note**: |
| Although message importing/auto-posting via smbutil is supported, the preferred solution is to use the ''[[module:postmsg]].js'' module (e.g. via [[module:binkit]]). | Although message importing/auto-posting via smbutil is supported, the preferred solution is to use the ''[[module:postmsg]].js'' module (e.g. via [[util:JSexec]]). |
| |
| |
| ===== See Also ===== | ===== See Also ===== |
| * [[module:binkit|Utilities]] | * [[util:index|Utilities]] |
| * [[module:binkit]] | * [[util:fixsmb]] |
| * [[module:binkit]] | * [[util:chksmb]] |
| |
| {{tag>smb msgbase subs}} | {{tag>smb msgbase subs}} |
