Many CLI commands that dump internal SSG databases output a dump with all internal fields and their values, so you should be warned about some peculiarities of JSON output.
Many CLI commands that dump internal SSG databases output a dump with all internal fields and their values, so you should be warned about some peculiarities of JSON output.
-
SSG can "spit out" tens and hundreds of megabytes of data in response to a command, if it is a dump command of the ''show all'' type. SSG cannot form such a response in a single block - it would have to allocate and reallocate many megabytes of memory, which may catastrophically affect the main work of SSG. Therefore, SCAT outputs the result of a command in packets of relatively small size (a few kilobytes of binary data at most). You can't see it externally, the fdpi_cli utility hides it when outputting it in text form. But you will see these bundles when unloading the response in JSON-format.
+
SSG can "spit out" tens and hundreds of megabytes of data in response to a command, if it is a dump command of the ''show all'' type. SSG cannot form such a response in a single block - it would have to allocate and reallocate many megabytes of memory, which may catastrophically affect the main work of SSG. Therefore, SSG outputs the result of a command in packets of relatively small size (a few kilobytes of binary data at most). You can't see it externally, the fdpi_cli utility hides it when outputting it in text form. But you will see these bundles when unloading the response in JSON-format.
The CLI exhaust in JSON format looks like this (generic skeleton):
The CLI exhaust in JSON format looks like this (generic skeleton):
