US Robotics USR2410 Manual de usuario Pagina 46

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 107
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 45
34
reconfigured, and the Click Modular Router started again. As this is what meshstart did,
memwatch then executed meshstart and exited.
The meshstart script redid all the steps previously done during boot up. When meshstart was
finished the system was setup once again as a mesh router, and memwatch was started to watch
for low memory again.
It was found that during heavy testing memwatch was effective in keeping the mesh routers up
and running. However, due to the nature of the mesh routing, by starting and stopping the Click
Modular Router, some machines were slow when re-establishing a connection to the mesh
network. During internet traffic usage with one or two clients, the memory leak in the Madwifi
module was not as noticeable, and memwatch usually did not need to release the memory.
6.1.3
Logging
As there was a need to keep track of the problems that occurred, and to determine the state of the
network while the mesh routers were running, relevant data was logged. These logs were
especially important during the testing of the implementation, as monitors were not available
when the mesh routers were deployed. These logs included the times at which meshstart was run,
and any problems that were encountered during its execution. Also logged were the times when
memwatch needed to free memory filled by the leak in the module. For general system
information, the syslog-ng system logger was used. This program was installed on each machine
using Gentoo's Portage distribution system. It logged operating system information such as
system initialization data, login times, and all data coming from the kernel. The system logger
also kept track of output from the Click Modular Router when it was run as a kernel module.
This data allowed the routing table changes and updates to be seen, as well as any errors that the
router encountered. Debug packet flow information from the Click Modular Router was also
printed to this log.
6.1.4
System Replication
Due to the software requirements of both Click and Madwifi, as well as the manual nature of the
Gentoo installation process, the time it took to set up a machine was sizeable. It was also
required that each machine be identical to each other. Due to these requirements, a process to
copy the entire hard drive from one system onto all the others was created. Due to the nature of
the Linux operating system, hard drives are represented as device files. To copy the entire
contents of one hard drive to another the commands in Table 6-2 were used.
Vista de pagina 45
1 2 ... 41 42 43 44 45 46 47 48 49 50 51 ... 106 107

Comentarios a estos manuales

Sin comentarios