You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The docker container needs to be restarted every time the configuration file is modified. Why can't the configuration file be read regularly according to the set time?
I don't know about best practices for Dockerized daemons, but in my experience typical daemons don't reload their config files automatically. I've seen some support reloading their config file on-demand when sent something like a SIGUSR1 or SIGHUP signal though.
Is the reason why it's particularly annoying to have to restart yt2pod because of issue #28?
frou
changed the title
能否定时读取配置文件?
Ability to reload the config file at runtime
Apr 15, 2021
I don't know about best practices for Dockerized daemons, but in my experience typical daemons don't reload their config files automatically. I've seen some support reloading their config file on-demand when sent something like a SIGUSR1 or SIGHUP signal though.
Is the reason why it's particularly annoying to have to restart yt2pod because of issue #28?
每次修改配置文件需要重启docker容器,为什么不能按照设定时间定时读取配置文件呢?
The text was updated successfully, but these errors were encountered: