Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to reload the config file at runtime #30

Open
jxjxjhjh opened this issue Apr 15, 2021 · 4 comments
Open

Ability to reload the config file at runtime #30

jxjxjhjh opened this issue Apr 15, 2021 · 4 comments

Comments

@jxjxjhjh
Copy link

每次修改配置文件需要重启docker容器,为什么不能按照设定时间定时读取配置文件呢?

@frou
Copy link
Owner

frou commented Apr 15, 2021

Sorry, you need to write in English here, please

@jxjxjhjh
Copy link
Author

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?

@frou
Copy link
Owner

frou commented 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?

@frou frou changed the title 能否定时读取配置文件? Ability to reload the config file at runtime Apr 15, 2021
@jxjxjhjh
Copy link
Author

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?

YES

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants