Handle error on redis, when redis socket directory does not exist.#8086
Handle error on redis, when redis socket directory does not exist.#8086KhDanial wants to merge 1 commit intoredis:unstablefrom KhDanial:unstable
Conversation
|
I'm still not convinced the default behavior should be to create the directory path. I would be open to it being a separate option. Do others have thoughts? |
you mean we set some config for this? |
|
i don't agree with this merge request. Environment variables should be checked carefully by users themselves if they want to deploy redis. Because redis can't and should not to match so many operating systems!!! |
|
I agree with @madolson about this, I don't think Redis should be doing this kind of setup and it's also not a generally common practice with other similar services. @KhDanial Is there any specific reason you can't just verify that the directory exists and with the right permissions before starting the BTW this implementation also introduces a security vulnerability as it uses an unbounded |
|
|
when we want to run redis server on system,it is possible that system does not have any directory for /var/run/redis
for this reason we add some code to check if we do not have this directory, created this directory with given permission, rerecursively