oputil.js fb scan improvement & fixes
* Start of --verbose for oputil.js in general (mostly placeholder at this point) * Fix --full-scan and rename to just --full
This commit is contained in:
@@ -209,7 +209,7 @@ function scanFileAreaForChanges(areaInfo, options, cb) {
|
||||
async.series(
|
||||
[
|
||||
function quickCheck(next) {
|
||||
if(options['full-scan']) {
|
||||
if(options['full']) {
|
||||
return next(null);
|
||||
}
|
||||
|
||||
@@ -229,6 +229,16 @@ function scanFileAreaForChanges(areaInfo, options, cb) {
|
||||
areaTag : areaInfo.areaTag,
|
||||
storageTag : storageLoc.storageTag
|
||||
},
|
||||
(stepInfo, next) => {
|
||||
if(argv.verbose) {
|
||||
if(stepInfo.error) {
|
||||
console.error(` error: ${stepInfo.error}`);
|
||||
} else {
|
||||
console.info(` processing: ${stepInfo.step}`);
|
||||
}
|
||||
}
|
||||
return next(null);
|
||||
},
|
||||
(err, fileEntry, dupeEntries) => {
|
||||
if(err) {
|
||||
console.info(`Error: ${err.message}`);
|
||||
@@ -477,7 +487,7 @@ function scanFileAreas() {
|
||||
}
|
||||
|
||||
options.descFile = argv['desc-file']; // --desc-file or --desc-file PATH
|
||||
options['full-scan'] = argv['-full-scan'];
|
||||
options['full'] = argv.full;
|
||||
|
||||
options.areaAndStorageInfo = getAreaAndStorage(argv._.slice(2));
|
||||
|
||||
|
||||
@@ -14,6 +14,7 @@ const usageHelp = exports.USAGE_HELP = {
|
||||
Global arguments:
|
||||
-c, --config PATH Specify config path (default is ${getDefaultConfigPath()})
|
||||
-n, --no-prompt Assume defaults (don't prompt for input where possible)
|
||||
--verbose Verbose output, where applicable
|
||||
|
||||
Commands:
|
||||
user User management
|
||||
@@ -131,7 +132,7 @@ scan arguments:
|
||||
DESCRIPT.ION file.
|
||||
|
||||
--update Attempt to update information for existing entries
|
||||
--full-scan Perform a full scan (default is quick)
|
||||
--full Perform a full scan (default is quick)
|
||||
|
||||
info arguments:
|
||||
--show-desc Display short description, if any
|
||||
@@ -152,7 +153,7 @@ General Information:
|
||||
Generally an area tag can also include an optional storage tag. For example, the
|
||||
area of 'bbswarez' stored using 'bbswarez_main': bbswarez@bbswarez_main
|
||||
|
||||
When performing an initial import of a large area or storage backing, --full-scan
|
||||
When performing an initial import of a large area or storage backing, --full
|
||||
is the best option. If re-scanning an area for updates a standard / quick scan is
|
||||
generally good enough.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user