Clipsal C-Bus Guia do Utilizador descarregar pdf (Página 22)

cbus Documentation, Release 0.1-dev

GETFILELIST

Client command:

GETFILELIST

Server response:

202 FILE1=C:\HomeGate\Projects\Current\EXAMPLEproj.tar.gz

Retrieves a list of “ﬁles” on the device associated with the project. This only returns the project ﬁle.

The path is faked by the daemon, with “EXAMPLE” replaced by the project name.

GETPROJ

Client command:

GETPROJ

Server response:

202-Port=8337

202 FILE=C:\HomeGate\Projects\Current\EXAMPLEproj.tar.gz

Returns the “project ﬁlename” for the contents of ﬂash partition 6. The path information is hard coded and fake, with

“EXAMPLE” replaced by the project name.

INSTALL

Client command:

INSTALL PROJECT example.tar.gz

Server response:

202 Port=8337

Starts an out of band transfer for overwriting the Wiser’s project ﬁle.

The server opens up another TCP server on a different port (on Wiser, this is always 8337) in order to accept the ﬁle

transfer out of band.

4.4.4 Project ﬁle transfer

Project ﬁle transfer is done on another port (always 8337), and initiated by the INSTALL command.

The client immediately sends:

FILE example.tar.gz

This is then immediately followed by a UNIX newline character, and then the ﬁle length as a 32-bit unsigned big-

endian integer.

Files must not be bigger than 512kB, or the transfer will be rejected by the Wiser. File names must end in ”.tar.gz”.

Projects must also not extract to a size greater than about 1 MiB. Wiser stores the contents of this archive in ramfs,

so larger archives will use all available RAM on the Wiser, and cannot be freed, leading to Linux’s oomkiller to

run or processes to fail to dynamically allocate memory. This has the potential in turn to partially brick the Wiser

18 Chapter 4. Wiser

1 2 ... 17 18 19 20 21 22 23 24 25 26 27 ... 59 60

Sem comentários

Clipsal C-Bus Guia do Utilizador Página 22