Skip to content

GSA PI lock mechanism while deduplicating files

AliTabAliTab GSAserlists.com
in GSA Platform Identifier

Hello @Sven and @s4nt0s,

It seems that GSA PI is not using a locking mechanism when it's deduplicating. So, when my own code wants to access the same files that are being deduplicated at the same time, PI will crash. Can you please check this and let me know where I can find the lock file to make my own code respect PI and avoid writing to the same file when it's being processed?

Thanks a lot!

Comments

  • SvenSven www.GSA-Online.de
    Im no in office today and will have to take a look on this tomorrow.
    Thanked by 1AliTab
  • AliTabAliTab GSAserlists.com
    Any update on this @Sven ?
  • SvenSven www.GSA-Online.de
    i need to reboot the system to activate vm options in bios....seems like the new system doesn't allow me to run my old VM ... needs to wait a bit.
    Thanked by 1AliTab
  • SvenSven www.GSA-Online.de
    OK now Im ready to debug this...however, I see no issue in allowing a file that is deduped to be read/write accessable while the end file is stored to .tmp and then moved over!?
  • AliTabAliTab GSAserlists.com
    edited September 21
    Thank you Sven for checking that. It seems you're right! I have figured out the bug on my own end.
  • AliTabAliTab GSAserlists.com



    Sven, there is a bug when "Append" is active. If the file doesn't exist, it should create the file and transfer the data. But now, if the file doesn't exist in the destination folder, the data will be lost.
Sign In or Register to comment.