é relacionado ao CrashPlan.
- Essas pastas são criadas para testar os recursos de gravação do CrashPlan e são normalmente excluídas automaticamente. No entanto, às vezes eles não são removidos corretamente.
Eu conversei com um agente de suporte do CrashPlan hoje.
A princípio ele disse que as pastas não tinham nada a ver com o CrashPlan, mas depois que eu enviei um link para o twitter comentário postado na pergunta, ele disse isso:
Thanks for your patience. After speaking with several colleagues on the support, I reached out to an engineer to get some additional details. As it turns out, that file IS related to CrashPlan. I sincerely apologize for inaccurately stating that was not the case.
In short, this occurs as part of a test process CrashPlan does to confirm it has read and write access on the computer. CrashPlan generally cleans up this file after the test is complete, but in some instances it is left behind. After more recent releases of the CrashPlan app, this behavior is far less common, but still possible.
I just confirmed you are safe to delete the file and it should no longer appear again unless a reinstall is necessary.
Ele então adicionou mais alguns detalhes:
To provide a little bit of background, the CrashPlan app needs read and write access on the drive in order for the backup to run. To test that it has write access on the computer, CrashPlan creates that file, which it is eventually supposed to “clean up” once the test is complete. Sometimes it can be blocked from cleaning it up, which will result in it being left behind.
Ele seguiu com:
I’d say, continue monitoring if it gets re-created for the time being. It may be indicative of a larger permissions issue with the CrashPlan app.
If it doesn’t appear again, I wouldn’t be concerned based on what I was told about the folder. It’s existence isn’t a problem. It just means CrashPlan couldn’t clean up after going through a basic process.
Finalmente, ele disse isso sobre possíveis problemas de segurança:
Absolutely not a security issue. If anything, there is a permissions issue where CrashPlan doesn’t have access to remove the file.