3 ms·
Troubleshooting what?
by ubercow13 6y ago
Troubleshooting what?
- gpvos 6y agoMaybe someone later has some legitimate edit they want to make to the file, which fails because it's immutable, which is in turn very hard to figure out. (E.g., I didn't know that there exists an "immutable" attribute.)
- protomyth 6y agoPut a comment in the file with the exact commands to turn on and off immutability. This is just good practice for most things. Having a maintenance text file with all the system stuff is a secondary good practice along with the comment.
- viraptor 6y agoFor example why some daemon in the future takes lots of CPU spinning and logging errors about not being able to write to a file it's configured to manage.
- Avamander 6y agoI'll be grateful that it let me know it's stupid and can't fail gracefully.
- ubercow13 6y agoSound like exactly the kind of badly designed daemon I'd be trying to protect against by making the change in the first place
- viraptor 6y agoLet's be honest: Next to no service is designed to expect immutable files. At best they're handling a situation of read-only filesystems. If they document how configure not writing to a file and instead of doing that, the user is marking the file immutable, I wouldn't blame the app design.