Long story short, I have a few systems that rely on over riding files on my VDS. Currently the folders that house the files are set as 'Read only'. At first I could not even remove the check marked box however after giving myself file owner of the specific file I could then edit it and remove the 'Read only' attribute, however upon closing out of the folder properties and then reopening, it is selected as 'Read only' again.
I've tried to run the "attrib -r +s C:\server\file\path" in command promot without successes as well, I am now clueless as to how I'm to fix this.
ALL the folders on the VDS are set to 'Read Only' so it doesn't matter where I move the file directory, and I can't launch all my applications as administrator to counteract this as it will give me errors on the programs I am running on my VDS (No way to avoid that).
Any help would be appreciated!
System folder attributes issue
-
JeffSutherland
- New to forums
- Posts: 3
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Wed Mar 12, 2014 4:14 pm
-
JeffSutherland
- New to forums
- Posts: 3
- Joined: Wed Mar 12, 2014 4:14 pm
Re: System folder attributes issue
Disregard, resolved it.
Re: System folder attributes issue
Can you elaborate how? If anyone else comes here with this issue it would be nice to have an answer for them.
Not a NFO employee
-
JeffSutherland
- New to forums
- Posts: 3
- Joined: Wed Mar 12, 2014 4:14 pm
Re: System folder attributes issue
Unfortunately this wasn't my issue, so I didn't actually fix this issue it just isn't the cause of it so I've left it for now as noone seems to know how, the only answer I get for the above is "I think its a bug with the windows 7 permissions".
Not sure how many people on this forum actually know about ArmA II servers, however this is my problem:
I'm running a Takistan Life server of which I'm running a third party statsave as ArmA II does not support player saving in the multiplayer files itself. The stat-save basically works like this:
You run it along side the multiplayer server and it creates a file for each player, while the server is running it creates a temporary file. upon restarting the actual ArmA server itself you have to 'flush' the stat-save which essentially changes the temporary files into permanent files housed within the files of the stat-save. If the player already has a permanent file it over rides the old file with the new.
My issue is, it wont flush properly, it wont over ride old files with new ones (Example, a permanent file is already created, when I flush the server it wont over ride the file with the new one, thus this is causing player rollbacks) and it isn't the stat-save itself as it works on my computer and it is the exact same files. The file paths for the stat-saving system are correct. So as far as I know this has something to do with the actual VDS I'm hosting it on something to do with permissions which is what is leading me on to think of this 'Read only' problem.
Anyone have any ideas?
Not sure how many people on this forum actually know about ArmA II servers, however this is my problem:
I'm running a Takistan Life server of which I'm running a third party statsave as ArmA II does not support player saving in the multiplayer files itself. The stat-save basically works like this:
You run it along side the multiplayer server and it creates a file for each player, while the server is running it creates a temporary file. upon restarting the actual ArmA server itself you have to 'flush' the stat-save which essentially changes the temporary files into permanent files housed within the files of the stat-save. If the player already has a permanent file it over rides the old file with the new.
My issue is, it wont flush properly, it wont over ride old files with new ones (Example, a permanent file is already created, when I flush the server it wont over ride the file with the new one, thus this is causing player rollbacks) and it isn't the stat-save itself as it works on my computer and it is the exact same files. The file paths for the stat-saving system are correct. So as far as I know this has something to do with the actual VDS I'm hosting it on something to do with permissions which is what is leading me on to think of this 'Read only' problem.
Anyone have any ideas?