CFDPRC(5)

🌸 CFDPRC 💅

okay bestie, so this is the manual page for cfdprc — the CCSDS File Delivery Protocol management commands file, from section 5 of the manual. yes, that's the same CFDPRC(5) you were looking for. pull up a chair, we're doing this 💖

---

✨ DESCRIPTION ✨

So here's the vibe: CFDP management commands get passed to cfdpadmin either from a file of text lines or interactively at cfdpadmin's command prompt, which is literally just a colon: (:). 🫶

The way this works is commands are interpreted line by line, with exactly one command per line — no stacking, no multitasking, one at a time, we're not doing chaos here. 🙈

The formats and effects of all the CFDP management commands are described below. yes, all of them. every single one. periodt. 👑

---

🎀 COMMANDS 🎀

• ? — the help command, and it's giving main character energy. It displays a listing of the commands and their formats. It's literally the same as the h command. 💫
• # — comment line, bestie. Lines beginning with # are not interpreted. That's it. That's the whole job. go off, king. 💀
• e { 1 | 0 } — the echo control command. Setting echo to 1 causes all output printed by cfdpadmin to be logged as well as sent to stdout. Setting echo to 0 disables this behavior. so 1 = yap and log, 0 = silence. 🌸
• v — version number. Prints out the version of ION currently installed. and HINT, bestie, listen: combine with the e 1 command to log the version number at startup. iykyk. 🔥
• 1 — the initialize command. and this one is important, so pay attention: until this command is executed, CFDP is not in operation on the local ION node, and most cfdpadmin commands will just... fail. so do this one first. it's giving prerequisites, it's giving gatekeeping. 👑
• i — the info command. This prints information about the current state of the local CFDP entity, including the current settings of all parameters that can be managed as described below. the full vibe check on your CFDP entity. 💅
• s 'UTS command' — the start command. This starts the UT-layer service task for the local CFDP entity. we're up and running, slay. ✨
• m discard { 0 | 1 } — the manage discard command. This enables or disables the discarding of partially received files upon cancellation of a file reception. half-finished files? we can toss 'em, or we can keep 'em. your call, bestie. 🎀
• m requirecrc { 0 | 1 } — the manage CRC data integrity command. This enables or disables the attachment of CRCs to all PDUs issued by the local CFDP entity. all of them. every last PDU. 💖
• m fillchar file_fill_character — the manage fill character command. This establishes the fill character to use for the portions of an incoming file that have not yet been received. The fill character is normally expressed in hex, e.g., 0xaa. so like, placeholder vibes for the missing bits. 🦋
• m ckperiod check_cycle_period — the manage check interval command. This establishes the number of seconds following reception of the EOF PDU — or following expiration of a prior check cycle — after which the local CFDP will check for completion of a file that is being received. like a lil reminder notification but make it protocol. ⏰
• m maxtimeouts check_cycle_limit — the manage check limit command. This establishes the number of check cycle expirations after which the local CFDP entity will invoke the check cycle expiration fault handler upon expiration of a check cycle. so there IS a limit to the patience. noted. 💀
• m maxtrnbr max_transaction_number — the manage transaction numbers command. This establishes the largest possible transaction number used by the local CFDP entity for file transmission transactions. After this number has been used, the transaction number assigned to the next transaction will be 1. it wraps around, bestie, we love a full circle moment. 🔄
• m segsize max_bytes_per_file_data_segment — the manage segment size command. This establishes the number of bytes of file data in each file data PDU transmitted by the local CFDP entity in the absence of an application-supplied reader function. yes, "in the absence of" — read the whole sentence, don't skim. 🙈
• m inactivity inactivity_period — the manage inactivity period command. This establishes the number of seconds that a CFDP file transfer is allowed to go idle before being canceled for inactivity. The default is one day. one whole day of silence and it's over. it's giving ghosting. 😭
• x — the stop command. This stops the UT-layer service task for the local CFDP engine. that's the opposite of s, we love symmetry. 🫶
• w { 0 | 1 | <activity_spec> } — the CFDP watch command. This enables and disables production of a continuous stream of user-selected CFDP activity indication characters. Here's the breakdown, bestie:
  • A watch parameter of 1 selects all CFDP activity indication characters.
  • 0 de-selects all CFDP activity indication characters.
  • Any other activity_spec such as p selects all activity indication characters in the string, de-selecting all others.

CFDP will print each selected activity indication character to stdout every time a processing event of the associated type occurs:

• p — CFDP PDU transmitted 📤
• q — CFDP PDU received 📥

• h — the help command. This displays a listing of the commands and their formats. It is the same as the ? command. twins. 💅

---

🧚 EXAMPLES 🧚

• m requirecrc 1 — Initiates attachment of CRCs to all subsequently issued CFDP PDUs. look at her go. iconic behavior. ⭐

m requirecrc 1

---

💜 SEE ALSO 💜

• cfdpadmin(1)
• bputa(1)

---

and that's the whole page, bestie, you ate that 🍓

this one's from perl v5.24.1, dated 2016-07-07 — shoutout to the CFDPRC(5) source, we love a vintage moment. mwah 💖💅✨