PAHO_CS_SUB_STATIC(1L)
β¨ PAHO_CS_SUB_STATIC(1L) β¨
okay bestie, sit down, hydrate, because we're talking about paho_cs_sub_static β that's section 1L of the manual, local commands, iykyk π
. This is the little program that receives (subscribes to) data from an MQTT server, and honestly? iconic. Let's get into it π«Ά
πΈ NAME πΈ
paho_cs_sub_static β receive (subscribe to) data from an MQTT server π
π SYNOPSIS π
paho_cs_sub_static [topic] [-t|--topic topic] [-c|--connection
connection] [-h|--host hostname] [-p|--port portnumber] [-i|--clientid
clientid] [-u|--username username] [-P|--password password]
[-k|--keepalive keepalive-timeout] [-V|--MQTT-version 31|311|5]
[-q|--qos 0|1|2] [-R|--no-retained] [--delimiter delimiter] [--no-
delimiter]
[--quiet] [--verbose] [--trace min|max|error|protocol]
[--will-topic will-topic] [--will-payload will-payload] [--will-retain]
[--will-qos 0|1|2]
[--cafile cafile] [--capath capath] [--cert certfile] [--key keyfile]
[--keypass password] [--ciphers cipher-string] [--insecure]
π¦ DESCRIPTION π¦
paho_cs_sub_static receives data from an MQTT server using the Eclipse Paho C client synchronous library (MQTTClient). no cap, that's the whole thing.
MQTT is a protocol β running over TCP/IP β that lets programs talk to each other so easily through a server. Messages get published to topics, and then delivered to literally anyone subscribed to those topics. The matching publisher program, paho_cs_pub, is the one that sends the MQTT messages. So they're a duo. main character + their bestie energy π
The default mode of operation is to output each message to stdout, terminated by the delimiter. simple. clean. slay β¨
π OPTIONS π
-t,--topicβ The MQTT topic to publish the data to.-c,--connectionβ The MQTT URI to connect to, a combination of transport prefix, host, port and, for websockets, topic. To connect using TCP, use thetcpprefix, for example:tcp://localhost:1883. An example using SSL/TLS:ssl://localhost:1883. An example for websockets, insecure:ws://localhost:1883/topic, and secure:wss://localhost:80/topic.-h,--hostβ The TCP/IP host name of the MQTT server to connect to. Along with the--portoption, an older alternative to using--connection.-p,--portβ The TCP/IP port number of the MQTT server to connect to. Along with the--hostoption, an older alternative to using--connection.-q,--qosβ The MQTT QoS on which to publish the message. The alternatives are0,1or2.-V,--MQTTversionβ The version of the MQTT protocol to use. Valid options are31(ormqttv31),311(mqttv311) and5(ormqttv5).--quietβ Do not print error messages. (shhh π€«)--traceβ Print library internal trace. Valid levels aremin,max,errorandprotocol.-R,--no-retainedβ Do not print messages which have the MQTT retained flag set.--delimiterβ The delimiter string to append to each message when printing. Defaults to newline.--no-delimiterβ Do not add a delimiter to each message when printing.--will-topicβ Sets the MQTT will message topic to publish to. If the application ends without sending an MQTT disconnect, the will message will be published to this topic.--will-payloadβ Only used ifwill-topicis set. Sets the MQTT will message to be published.--will-qosβ Only used ifwill-topicis set. Sets the MQTT QoS at which the will message is published. The alternatives are0,1or2.--will-retainβ Only used ifwill-topicis set. Sets the MQTT retained flag on the will message.--cafileβ Only used with a TLS connection. The name of a file for the OpenSSL trust store.--capathβ Only used with a TLS connection. The name of a directory holding OpenSSL trusted certificates.--certβ Only used with a TLS connection. The name of a file for the TLS keystore containing a client certificate to be presented.--keyβ Only used with a TLS connection. The name of a file containing the client private key.--keypassβ Only used with a TLS connection. The password for the client private key file, if needed.--ciphersβ Only used with a TLS connection. A list of cipher suites that the client will present to the server during the TLS handshake.--insecureβ Only used with a TLS connection. Don't check that the server certificate common name matches the hostname.
bestie, just a heads up: --insecure means it does not check that the server certificate common name matches the hostname. that's the whole point of the flag, and that's the whole risk of the flag. know what you're doing π
π SEE ALSO π
paho_c_pub(1) paho_c_pub_static(1) paho_c_sub(1) paho_c_sub_static(1) paho_cs_pub(1) paho_cs_pub_static(1) paho_cs_sub(1)
and that's the page, periodt π go read the sibling pages, they're all in the same friend group fr fr.
http://eclipse.org/paho β 31 December 2020 β (v1.3.8) β PAHO_CS_SUB_STATIC(1L) π bye bestie, happy subscribing π¦π
π¦ where this page comes from
- debian trixie: paho.mqtt.c-examples 1.3.14-2 Β· EPL-2.0
- ubuntu noble: paho.mqtt.c-examples 1.3.13-1build2 Β· EPL-2.0
- ubuntu questing: paho.mqtt.c-examples 1.3.14-2
- ubuntu resolute: paho.mqtt.c-examples 1.3.15-1 Β· EPL-2.0
- ubuntu stonking: paho.mqtt.c-examples 1.3.16+ds-1build1 Β· EPL-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms