- -
- NOTE: Some changes may require a restart to take effect. -
+ + +
+ NOTE: Some changes may require a restart to take effect. +
- The Java clients listed below are started by the router and run in the same JVM. -
- All changes require restart to take effect. To change other client options, edit the clients.config file. -
- The Java web applications listed below are started by the webConsole client and run in the same JVM as the router. - They are usually web applications accessible through the router console. - They may be complete applications (e.g. i2psnark), - front-ends to another client or application which must be separately enabled (e.g. susidns, i2ptunnel), - or have no web interface at all (e.g. addressbook). -
- A web app may also be disabled by removing the .war file from the webapps directory; - however the .war file and web app will reappear when you update your router to a newer version, - so disabling the web app here is the preferred method. -
- All changes require restart to take effect. To change other webapp options, edit the webapps.config file. -
+ The Java clients listed below are started by the router and run in the same JVM. +
+ +
+ All changes require restart to take effect. To change other client options, edit the clients.config file. +
+ The Java web applications listed below are started by the webConsole client and run in the same JVM as the router. + They are usually web applications accessible through the router console. + They may be complete applications (e.g. i2psnark), + front-ends to another client or application which must be separately enabled (e.g. susidns, i2ptunnel), + or have no web interface at all (e.g. addressbook). +
+ A web app may also be disabled by removing the .war file from the webapps directory; + however the .war file and web app will reappear when you update your router to a newer version, + so disabling the web app here is the preferred method. +
+ All changes require restart to take effect. To change other webapp options, edit the webapps.config file. +
-
+
- - - -
- - - <% if (! "".equals(peer)) { %> - <---- click to verify action - <% } %> -
- <% long speed = 0; long capacity = 0; - if (! "".equals(peer)) { - // get existing bonus values? - } - %> - Speed: - - Capacity: - - -
+ + + +
+ + + <% if (! "".equals(peer)) { %> + <---- click to verify action + <% } %> +
+ <% long speed = 0; long capacity = 0; + if (! "".equals(peer)) { + // get existing bonus values? + } + %> + Speed: + + Capacity: + + +
Graceful shutdown lets the router satisfy the agreements it has already made - before shutting down, but may take a few minutes. If you need to kill the - router immediately, that option is available as well.
If you want the router to restart itself after shutting down, you can choose one of - the following. This is useful in some situations - for example, if you changed - some settings that client applications only read at startup, such as the routerconsole password - or the interface it listens on. A graceful restart will take a few minutes (but your peers - will appreciate your patience), while a hard restart does so immediately. After tearing down - the router, it will wait 1 minute before starting back up again.
On the windows platform, there is a small application to sit in the system - tray, allowing you to view the router's status (later on, I2P client applications - will be able to integrate their own functionality into the system tray as well). - If you are on windows, you can either enable or disable that icon here.
You can control whether I2P is run on startup or not by selecting one of the - following options - I2P will install (or remove) a service accordingly. You can - also run the install_i2p_service_winnt.bat (or - uninstall_i2p_service_winnt.bat) from the command line, if you prefer.
install_i2p_service_winnt.bat
uninstall_i2p_service_winnt.bat
Note: If you are running I2P as service right now, removing it will shut - down your router immediately. You may want to consider shutting down gracefully, as - above, then running uninstall_i2p_service_winnt.bat.
At times, it may be helpful to debug I2P by getting a thread dump. To do so, - please select the following option and review the thread dumped to - wrapper.log.
I2P's main configuration interface is this web console, so for your convenience - I2P can launch a web browser pointing at - http://127.0.0.1:7657/index.jsp whenever - the router starts up.
Graceful shutdown lets the router satisfy the agreements it has already made + before shutting down, but may take a few minutes. If you need to kill the + router immediately, that option is available as well.
If you want the router to restart itself after shutting down, you can choose one of + the following. This is useful in some situations - for example, if you changed + some settings that client applications only read at startup, such as the routerconsole password + or the interface it listens on. A graceful restart will take a few minutes (but your peers + will appreciate your patience), while a hard restart does so immediately. After tearing down + the router, it will wait 1 minute before starting back up again.
On the windows platform, there is a small application to sit in the system + tray, allowing you to view the router's status (later on, I2P client applications + will be able to integrate their own functionality into the system tray as well). + If you are on windows, you can either enable or disable that icon here.
You can control whether I2P is run on startup or not by selecting one of the + following options - I2P will install (or remove) a service accordingly. You can + also run the install_i2p_service_winnt.bat (or + uninstall_i2p_service_winnt.bat) from the command line, if you prefer.
Note: If you are running I2P as service right now, removing it will shut + down your router immediately. You may want to consider shutting down gracefully, as + above, then running uninstall_i2p_service_winnt.bat.
At times, it may be helpful to debug I2P by getting a thread dump. To do so, + please select the following option and review the thread dumped to + wrapper.log.
I2P's main configuration interface is this web console, so for your convenience + I2P can launch a web browser pointing at + http://127.0.0.1:7657/index.jsp whenever + the router starts up.