These are monitoring pages for the different indexing queues.
YaCy knows 5 different ways to acquire web indexes. The details of these processes (1-5) are described within the submenu's listed above which also will show you a table with indexing results so far. The information in these tables is considered as private, so you need to log-in with your administration password.
Case (6) is a monitor of the local receipt-generator, the opposed case of (1). It contains also an indexing result monitor but is not considered private since it shows crawl requests from other peers.
The image above illustrates the data flow initiated by web index acquisition. Some processes occur double to document the complex index migration structure.
::This is the list of web pages that this peer initiated to crawl, but had been crawled by other peers. This is the 'mirror'-case of process (6).
Use Case: You get entries here, if you start a local crawl on the 'Index Creation'-Page and check the 'Do Remote Indexing'-flag. Every page that a remote peer indexes upon this peer's request is reported back and can be monitored here.
::This index transfer was initiated by your peer by doing a search query. The index was crawled and contributed by other peers.
Use Case: This list fills up if you do a search query on the 'Search Page'
::The url fetch was initiated and executed by other peers. These links here have been transmitted to you because your peer is the most appropriate for storage according to the logic of the Global Distributed Hash Table.
Use Case: This list may fill if you check the 'Index Receive'-flag on the 'Index Control' page
::These web pages had been indexed as result of your proxy usage. No personal or protected page is indexed; such pages are detected by Cookie-Use or POST-Parameters (either in URL or as HTTP protocol) and automatically excluded from indexing.
Use Case: You must use YaCy as proxy to fill up this table. Set the proxy settings of your browser to the same port as given on the 'Settings'-page in the 'Proxy and Administration Port' field.
::These web pages had been crawled by your own crawl task.
Use Case: start a crawl by setting a crawl start point on the 'Index Create' page.
::These pages had been indexed by your peer, but the crawl was initiated by a remote peer. This is the 'mirror'-case of process (1).
Use Case: This list may fill if you check the 'Accept remote crawling requests'-flag on the 'Index Crate' page
#(/process)# #(table)#The stack is empty.
::#(size)# Showing all #[all]# entries in this stack. :: Showing latest #[count]# lines from a stack of #[all]# entries. #(/size)#
| #(showInit)#:: | Initiator | #(/showInit)# #(showExec)#::Executor | #(/showExec)#Modified Date | #Words | Title | URL |
| #(showInit)#:: | #[initiatorSeed]# | #(/showInit)# #(showExec)#::#[executorSeed]# | #(/showExec)##[moddate]# | #[wordcount]# | #[urldescr]# | #(available)# -not cached- :: #[url]# #(/available)# |