It seems that fbitdump is performing a strict concatenation of the paths provided using the '-M' and '-r' parameters. This can easily lead to errors and should be very simple to fix. Example:
user@machine:~$fbitdump -C fbitdump.xml -M /<path>/0 -r 2014/10/28/ic20141028132900
Cannot open directory "/<path>/02014/10/28/ic20141028132900/"
No tables found in specified directory
To fix this kind of errors, fbitdump should check whether an additional '/' must be inserted.
It seems that fbitdump is performing a strict concatenation of the paths provided using the '-M' and '-r' parameters. This can easily lead to errors and should be very simple to fix. Example:
To fix this kind of errors, fbitdump should check whether an additional '/' must be inserted.