DigitalVolcano Software Support

The Log file, by default, looks to end up in Documents.
The Log file, can be named anything & be just about anywhere you want it.

Options | Settings | General -> Log

The log can be manipulated as you want - outside of DC (& while DC is not running a scan).
If too big, edit it & purge some data, or have it open with a different editor/viewer.
Need a backup of it, copy it elsewhere.
Don't need it, delete it & it should automatically recreate.

If you change the location of the Log file, I would think that any existing Log file would simply remain where they were.
So if originally it was in Documents, & you then later set the location to C:/LOGS/, the Documents copy would persists, & new entries would end up in C:/LOGS/. If then, at some later time, looked at the copy in Documents, it would appear to "not be updating" - cause you've stopped writing to it. Though the copy in C:/LOGS/ should be updating.

Hashes & whatnot are stored in %appdata%/Roaming/DigitalVolcano/DuplicateCleaner.
(Now that is something I'd like to be able to specify the location of.

As it is, E: is my system drive, & it is almost exclusively my OS. I do not store any "data" there - though I did not redirect in any manner. I just set programs to store data - where I want them to. [I do "move" my %TMP% directory, outside of E:, by setting its' environment variable to point where I want it.] And most all comply with that. A few odd ones, DC included, do no allow specifying where its' data files reside, so they do end up writing to my E: drive, & in %appdata% at that.)


And if size is an issue, you could even change the log file name, say from "name.log file.txt" to "name.dc5log" & have a fast editor/viewer that only opens .dc5log files (while still keeping your wanted program that deals with .txt). (And that really only applies to opening the Log directly from within DC, 'View log file', as it will use your default editor, based upon extension, to open the Log. Outside of DC, you can use whatever you want - using Open With, right-click the file, Open With.)

I realize all of that. I must have an permission setup that is weird in my relocated (per windows feature). It is not about the file name. but about the writing permission. I should have made my most recent tests before sharing here.. It does seems more about my file system history than DC...
Although it is only DC that gives me such problem right now. It can be worked around easily. No need for this thread to continue as request for help, it is more of a report about the possiblility that permissions of software in given user folder (while relocated maybe, perhaps just permission at the folder, as DC5 keeps the exact folder path of the target once chosen through the default dialog box that uses the user "Document" as default, so it might not be about writing permission thorugh the redirection (or symlink) but really the permission at the target drive and folder where I chose to put the file.

I am slow these days.. So I might keep adding more information later to conclude this. Eventually.