I'm using Core 17.0 on x86_64
Is there a handy way to get the "immutable" attribute of a file to persist across a backup and restore cycle?
My issue is this: I have an application (emelfm2) that insists on changing the value of a certain setting in its config file to its default value when the program is closed and restarted.
Alarmingly, it does this even when the config file's ownership is changed to root:root and all write permissions are removed and the application is -not- running as root..
Using chattr to set the immutable attribute solves the problem, but doesn't survive a reboot with backup and restore because the file is restored without "immutable" set..
As one-off, I could put a line in bootsync.sh to set the immutable attribute, but that feels clumsy so I'm looking for a more elegant solution.
- use persistent HOME, which I don't want to do
- remaster the emelfm2 extension to include the config file on r/o media (which would prevent me from ever changing any other setting)
- use a different file manager, which I don't want to do
but none of those really seem ideal either.
The file in question is
~/.config/emelfm2/config-C.
The setting within the file has to do with the way file dates are displayed. There is a drop down list to select any of several preconfigured date formats (all of which are stupid) or "strftime() format provided below" with a box to enter a custom time format. When the setting resets to default, it doesn't lose the custom format, it just forgets that its supposed to actually use it.
I think emelfm2 is an abandoned application so, while it would be ideal to have the application fixed, I don't think that's going to happen. I'm comfortable with making the config file immutable and, if I have to, I'll reinstate the immutability at boot time but I'm hoping someone will mention something I've missed that allows the immutable attribute to be saved. Feel free to say, "Well, dumbhead, did you try ...."
Any ideas?
Welcome
FAQ
Downloads
Wiki
Recent Posts