package net.i2p.router.startup
The I2P startup package loads configuration when I2P is started.
The startup consists of a number of different jobs, like loading data from files for 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
- All Classes and InterfacesClassDescriptionThis actually boots almost everything.Start up the network database.Start up the peer manager.For future restricted routes.Contains a really simple ClientApp "structure" and some static methods so they can be used both by
LoadClientAppsJoband by the configuration page in the router console.Warning - misnamed.Run any client applications specified inclients.config.Public for router console only, not for use by others, subject to change.Runner that loads and starts one client app.Job waiting for the netdb before loading a client.Run once or twice at startup byStartupJob, and then runs BootCommSystemJob.Key data container for router information.Second migration, as of 2.9.0.Provides a relative working directory for i2p based upon properties set by the parent process.This used be called fromStartAcceptingClientsJobbut is now disabled.Notify the router of events, and provide methods for client apps to find each other.Start the I2CP interface.The StartupJob should be run once on router startup to initialize the system and set things in motion.Provides the working directory for i2p.