-
Notifications
You must be signed in to change notification settings - Fork 6
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
Make new exitnodes publish their routes to the monitor by default #21
Comments
Working on this Tonight, is there a reason why theres two different scripts? they both need to run? should they stay separate for some reason? |
It's just a historical reason. The monitor.sh script is not really needed anymore, but the monitor code needs to be changed to no longer expect it. The monitor can derive the same info from the newer post-routing-table.sh. Maybe now's a good time to get rid of monitor.sh |
i realize that monitor.sh says that, but monitor.sh is the actual request to update the total routes and total gateways. If we can just use json request to do everything in the post-routing-table.sh, I'll have to look at the server side code. |
@jnull it looks like I made an issue for this in January :) |
I made an ugly PR here: #25 but it should auto start updating monitor. |
Currently this setup has to be done manually, but it should be a part of create-exitnode.sh.
Let's keep using systemd timers, just like we do here: https://github.com/sudomesh/exitnode/blob/master/src/etc/systemd/system/babeld-monitor.timer
The scripts that need to be run are https://github.com/sudomesh/monitor/blob/master/monitor.sh and https://github.com/sudomesh/monitor/blob/master/post-routing-table.sh, every 2 minutes.
The text was updated successfully, but these errors were encountered: