Opened 4 years ago

Closed 4 years ago

#19265 closed defect (fixed)

Start hourly updater using a start/stop script rather than crontab

Reported by: karsten Owned by:
Priority: Medium Milestone: Onionoo 3.1-1.0.0
Component: Metrics/Onionoo Version:
Severity: Normal Keywords:
Cc: iwakeh Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


There are multiple reasons for doing this. The most recent example: we reduce the risk of leaving the crontab line unchanged when we deploy a new version (see re-opened #19154).

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by iwakeh

I second this!

The internal scheduler (i.e. run jar without additional arguments) works fine,
I used it for some time on a (now gone) development mirror w/o a script though.

The script will be straight forward for start and stop.

If a status option is to be supplied too, it first could basically look whether the process is still there. A future option would be to use java management extensions for receiving status info.
(That would be a new trac issue.)

comment:2 Changed 4 years ago by iwakeh

Milestone: Onionoo 3.1.1

comment:3 Changed 4 years ago by karsten

Milestone: Onionoo 3.1.1Onionoo 3.1-1.0.0

Milestone renamed

comment:4 Changed 4 years ago by iwakeh

Resolution: fixed
Status: newclosed

Actually, this task is obsolete as Onionoo has an hourly scheduler build-in, cf. #14826.

There are now examples for start-stop-scripts in the mirror section of Metrics' wiki.


Note: See TracTickets for help on using tickets.