This port currently does just ship the binary and manpage but doesn't include a startup script.
It would be nice to add
- a startup script for the RTR server use case
- a default folder structure for TALs and the downloaded resources
- a routinator user that is used to run the daemon
(In reply to C from comment #0)
These omission were intentional because the system changed a lot in earlier versions. Indeed, it is time to add these.
I'll whip something up for the next release or create a patch whatever comes first. In case you rolled your own, I'm happy to use that as a start.
thanks for considering this improvement request.
Do you have any time plans for this?
(In reply to C from comment #2)
Two days ago I was about to release a patch which has the script included. But then I was told that there will be a release in a week or so which changes part of the interface and probably also the startup method.
Therefore I decided to wait for that release for the time being (unless people get really desperate)
Since fixup release (0.6.1) is scheduled for tomorrow, will this also bring the parts missing for this bugzilla entry?
I was about to shop 0.6.0 but indeed, now will wait until 0.6.1 is ready. No point in shipping a broken version.
A commit references this bug:
Date: Thu Nov 28 10:57:01 UTC 2019
New revision: 518574
Update to 0.6.2.
- Add a startup script.
- Add a separate user/group for the daemon to use.
Submitted by: Jaap Akkerhuis <jaap@NLnetLabs.nl> (maintainer)
Overtaken by events.
As stated in comment #6, a startup script is now part of the port.
- Assign to committer to resolve
- Track non-merge