Package net.i2p.router.startup
package net.i2p.router.startup
The I2P startup package loads the configuration when I2P is started.
The startup consists of a number of different jobs, like loading data from files for the network database, creating new router information (keypairs), and so on.
Calling order: StartupJob LoadClientAppsJob starts clients and queues delayed client jobs start stats publisher LoadRouterInfoJob RebuildRouterInfoJob if necessary CreateRouterInfoJob if necessary BootCommSystemJob allow parallel operation in job queue BootNetworkDbJob starts netdb BuildTrustedLinksJob (never used) BootPeerManagerJob starts peer manager start comm system start tunnel manager StartAcceptingClientsJob starts client manager ReadConfigJob loops every 30 seconds
-
ClassDescriptionThis actually boots almost everythingstart up the network databasestart up the peer managerFor future restricted routes.Contains a really simple ClientApp "structure" and some static methods so they can be used both by LoadClientAppsJob and by the configuration page in the router console.Warning - misnamed.Run any client applications specified in clients.config.Public for router console only, not for use by others, subject to changeRun once or twice at startup by StartupJob, and then runs BootCommSystemJobMigrate the clients.config and jetty.xml files from Jetty 5/6 to Jetty 7/8.Get a relative working directory for i2p based upon properties by parent process.This used be called from StartAcceptingClientsJob but is now disabled.Notify the router of events, and provide methods for client apps to find each other.start I2CP interfaceThe StartupJob should be run once on router startup to initialize the system and set things in motion.Get a working directory for i2p.