Editing Sage.prop in docker- file always in use?

[btrcp2000]

I could swear this wasn't always the case since i first started playing with unraid a few months back, but for the past week or so, every time I edit sage.prop, notepad++ complains that it may be open somewhere and won't save it. I have to save it as something else, and then drag and drop/replace using windows file explorer. This is with the sage docker stopped.

[stuckless]

Originally Posted by btrcp2000

I could swear this wasn't always the case since i first started playing with unraid a few months back, but for the past week or so, every time I edit sage.prop, notepad++ complains that it may be open somewhere and won't save it. I have to save it as something else, and then drag and drop/replace using windows file explorer. This is with the sage docker stopped.

Have you updated notepad++ recently? Does notepad++ create a lock file for opened file, and does that exist? (some editors do this, to prevent editing the same file -- but if the editor is unexpected closed, then it might not get cleaned up).

[btrcp2000]

It's a fresh install of notepad++ on a fresh VM, all from last night. Only happens when I am editing the docker one via Win Exp. I also have windows sage installed on the same VM, and can edit/save without the error. Must be an issue with file permissions. In Windows explorer, I can see that all users (everyone, users, nobody) have Read, but only Nobody has Write. no users have Full, and when i go to change it. I get:

Unable to save permission changes on Sage. Access is denied.

[wayner]

You might have to change the permissions from the bash prompt in Linux.