@@ -108,15 +108,22 @@ file.
108108
109109 .. note ::
110110
111- Remote file access is implemented by transferring an
112- `αcτµαlly pδrταblε εxεcµταblε <https://justine.lol/ape.html >`_ to the
113- destination and invoking it. An APE binary can run on most any x86_64
114- machine and OS (i.e. MacOS, Linux, FreeBSD, Windows). The binary is
115- baked into the lnav executable itself, so there is no extra setup that
111+ Remote file access is implemented through a "tailer" executable that is
112+ transferred to the host. The tailer handles requests from lnav for
113+ synchronizing file blocks, completing path names, previewing files,
114+ and so on.
115+
116+ There are two implementations of the tailer: Python3 and an
117+ `αcτµαlly pδrταblε εxεcµταblε <https://justine.lol/ape.html >`_.
118+ If the target host does not have Python3 installed, the APE binary will
119+ be used. An APE binary can run on most any x86_64 machine and OS
120+ (i.e. MacOS, Linux, FreeBSD, Windows). The implementations are baked
121+ into the lnav executable itself. So, there is no extra setup that
116122 needs to be done on the remote machine.
117123
118- The binary file is named ``tailer.bin.XXXXXX `` where *XXXXXX * is 6 random digits.
119- The file is, under normal circumstancies, deleted immediately.
124+ The tailer is copied to the user's home directory and is named
125+ ``tailer.bin.XXXXXX `` where *XXXXXX * is 6 random digits.
126+ Under normal circumstances, the file should be deleted immediately.
120127
121128Command Output
122129^^^^^^^^^^^^^^
0 commit comments