Unverified Commit f0373f72 authored by Binbin's avatar Binbin Committed by GitHub
Browse files

Fix outdated protected-mode documentation in sentinel.conf (#9896)

In 666b3437, we modified the default value of protected-mode
from yes to no.

However, this change is not mentioned in sentinel.conf.
Looking at the sentinel.conf alone, it is easy to make
people think that in sentinel mode, we hava truned on
the protected-mode.
parent a7726cdf
# Example sentinel.conf # Example sentinel.conf
# *** IMPORTANT *** # By default protected mode is disabled in sentinel mode. Sentinel is reachable
# # from interfaces different than localhost. Make sure the sentinel instance is
# By default Sentinel will not be reachable from interfaces different than # protected from the outside world via firewalling or other means.
# localhost, either use the 'bind' directive to bind to a list of network protected-mode no
# interfaces, or disable protected mode with "protected-mode no" by
# adding it to this configuration file.
#
# Before doing that MAKE SURE the instance is protected from the outside
# world via firewalling or other means.
#
# For example you may use one of the following:
#
# bind 127.0.0.1 192.168.1.1
#
# protected-mode no
# port <sentinel-port> # port <sentinel-port>
# The port that this sentinel instance will run on # The port that this sentinel instance will run on
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment