Again, you can set this in the shell, so I think this is a needless addition

It's cheap and easy to add these options, but incredibly hard to remove, so I am personally against this. Lets see what others say.

I found it quite difficult to work out how to get the umask set correctly in the init script due to the multiple levels of escaping required.

I don't necessarily disagree with you though but the end result is this lets me reliably set the umask which is critical to having permissions set correctly.

Sure, but you could make the same argument about environment variables, and we should add -env, because of multiple levels of escaping. Multiple levels of escaping is sort of not our problem and us having to work around it seems wrong.

Again, lets see what others have to say.

I agree that while there is nothing technically
wrong with the implementation here this is not something we want to add. The umask is better set in a small shell script or as an option in the service manager, whichever such is used. It would also be odd to add something that doesn’t make sense on Windows and is silently ignored there.