You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just noticed after running multiple times the dirlog update that it readds nuked directories even if they are already in the dirlog:
DIRLOG: /site/incoming/stuff/DIR1 - 167 Mbytes in 14 files - created 26 Mar 2017 07:44:01 by 206.500 [1]
DIRLOG: /site/incoming/stuff/DIR2 - 196 Mbytes in 16 files - created 26 Mar 2017 07:44:00 by 206.500 [1]
DIRLOG: /site/incoming/stuff/DIR3 - 218 Mbytes in 18 files - created 26 Mar 2017 07:44:01 by 241.900 [1]
[12:39:22] [L] site search DIR1
[12:39:22] [L] 200- (Values displayed after dir names are Files/Megs/Age)
[12:39:22] [L] 200- Doing case-insensitive search for 'DIR1':
[12:39:26] [L] 200- /incoming/stuff/DIR1 *NUKED*
[12:39:26] [L] 200- /incoming/stuff/DIR1 *NUKED*
[12:39:26] [L] 200- /incoming/stuff/DIR1 *NUKED*
[12:39:26] [L] 200- /incoming/stuff/DIR1 *NUKED*
The text was updated successfully, but these errors were encountered:
Hi,
Just noticed after running multiple times the dirlog update that it readds nuked directories even if they are already in the dirlog:
The text was updated successfully, but these errors were encountered: