Contents   Index

Communication with TACO

Explicit use of TACO was narrowed down to link monitoring using the link daemon, linkd, communicating with the client applications through a newly written pesto-taco daemon, ptacod, and the file ".pesto.commstat", see Figures 6.1 (p. ), 6.2 (p. ), and 6.3 (p. ). The pesto-taco daemon is based on code from the TACO user guide [12].

Figure 6.1: PeStO-TACO daemon (1)

Figure 6.2: PeStO-TACO daemon (2)

Figure 6.3: PeStO-TACO communication

Figure 6.4 (p. ) shows the data flow. The arrow from the socket interface to the linkd daemon should not be taken too literally - it is more complicated than so, see [11]. An overview of the files are given in Section 6.4.

The system naturally uses TACO implicitly when it (TACO) is running, since the TACO system handles the forwarding of all IP and UDP packets to and from the client when weakly connected, see [11].

Figure 6.4: Data flow

  Contents   Index