plot command should reload config after sleeping (with alternate request)
See original GitHub issueI would like plotman plot
to be run as a background job using nohup
(or in my specific case, as the docker entrypoint command). As a result, I want to be able to make changes to the plotman config without having to restart the background job.
I see 2 ways to do this:
- Plotman re-reads the config after sleeping. This is probably best for most users so they don’t need to know as much, but might require significant changes.
- Add a parameter like
plotman plot -q
orplotman plot -n 5
.-q
in this case would run the plotting check and quit.-n 5
would run it 5 times (with the specified sleep in between) and then quit. In either scenario, I would set the docker entrypoint to be a loop with my own sleep timer.
otherwise, fantastic project and thank you!
Issue Analytics
- State:
- Created 2 years ago
- Comments:10
Top Results From Across the Web
Plotting in a non-blocking way with Matplotlib - Stack Overflow
Substitute backend command should run first. import matplotlib matplotlib.use('TkAgg'). My answer come from Pycharm does not show plot.
Read more >Manpage - Monitorix
This is a list of groups of CPU sensors you want to monitor with the same names as they appear in your sensors(1)...
Read more >Systemd - ArchWiki - Arch Linux
See systemd. unit(5) § UNIT FILE LOAD PATH for the directories where available unit files can be found. This does not ask the...
Read more >How do I disable my system from going to sleep? - Ask Ubuntu
On Ubuntu 16.04 LTS, I successfully used the following to disable suspend: sudo systemctl mask sleep.target suspend.target hibernate.target hybrid-sleep.
Read more >Service start request repeated too quickly, refusing to start limit
The default limit is to allow 5 restarts in a 10sec period. If a service goes over that threshold due to the Restart=...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
if you are not running inside docker it should work that way. Plotman is stateless and doesnt remain on anything like a database or something in ram… it just collects what it needs, so you can safely restart plotman.
Nice work! I solved it by making plot and archive configurable and let a loop run in entrypoint that starts plotman $command every 10 seconds if it isnt running. this way you can let the container do its thing, change config and reload config by simply
docker-compose exec plotman bash -c "killall plotman"
. I should throw this into github aswell… Because with this its possible to use the plotman archiver under windows ^^