NUTSCAN_DISPLAY_PARS(3)

πŸ’– NUTSCAN_DISPLAY_PARS(3) πŸ’–

okay bestie, welcome to the NUT Manual ✨ this is the page for nutscan_display_parsable, and yes it's spelled like that, we don't make the rules 🫢


✨ NAME ✨

nutscan_display_parsable β€” the lil function that prints out the nutscan_device_t struct you hand it, straight to stdout πŸ’…


🌸 SYNOPSIS 🌸

#include <nut-scan.h>

void nutscan_display_parsable(nutscan_device_t * device);

πŸ¦‹ DESCRIPTION πŸ¦‹

so like. nutscan_display_parsable() takes everything in device and dumps all the NUT devices it holds onto stdout. and the way it prints them? deliberately in a format that's super easy to parse, no cap. here's the shape:

<driver type>:driver="<driver name>",port="<port type>"[,<optional parameter 1>="<optional data 1>",<optional parameter 2>="<optional data 2>",...]
  • <driver type> is gonna be one of USB, SNMP, XML, NUT, IPMI or AVAHI. that's the whole roster, periodt.
  • <driver name> is the name of the driver's binary that goes with this device πŸ‘‘
  • <port type> and <optional parameter X> both depend on <driver name>, so like, go read the matching driver's man page, iykyk πŸ“–
⚠️ heads up bestie: this format is for machine consumption, fr fr. so it does not come with the sanity checks that you'd get from the display method for the ups.conf file format. it's giving raw data, not vibes-validated data 😭

🌈 SEE ALSO 🌈


and that's the whole page, you ate it πŸ’… Network UPS Tools 2.8.5, dated 10/07/2026 β€” slay, go parse some devices bestie πŸŽ€πŸ§šπŸ’œ

πŸ“¦ where this page comes from