AirInvServer(1)
β¨ AirInvServer(1) β¨
okay bestie, this is the page for AirInvServer from the General Commands Manual π I read the whole thing so you don't have to π
β¨ NAME β¨
AirInvServer - a ZeroMQ-based server binary that exposes the AirInv library as a service π¦
β¨ SYNOPSIS β¨
AirInvServer [--prefix] [-v|--version] [-h|--help] [-b|--builtin]
[-f|--for_schedule] [-i|--inventory <path-to-inventory-input-file>]
[-s|--schedule <path-to-schedule-input-file>] [-o|--ond <path-to-ond-input-file>]
[-y|--yield <path-to-yield-input-file>] [-t|--protocol <server network protocol>]
[-a|--address <server host address>] [-p|--port <server host port>]
[-l|--log <path-to-output-log-file>]
β¨ DESCRIPTION β¨
So AirInvServer is a little program that wraps the AirInv library and serves it up as a ZeroMQ-based server πΈ The server listens for requests and answers with JSON-formatted messages. Usually a Django-based Web app is the one talking to it, so the end user gets a clean and light interface. Iconic behavior, honestly π
AirInvServer accepts the following options:
--prefixβ Shows the AirInv installation prefix π-v,--versionβ Prints the currently installed version of AirInv to the standard output β¨-h,--helpβ Shows that help message and displays usage π-b,--builtinβ The sample BOM tree can be built-in or parsed from an input file. If you go the input file route, you have to pass it with either the-i/--inventoryoption or the-s/--scheduleand-o/--ondoptions together π§-f,--for_scheduleβ The BOM tree gets built from a schedule file instead of an inventory dump π¦-i,--inventory <path-to-input-file>β The path (absolute or relative) to the (CSV) input file that describes the inventory (flight-date) details π-s,--schedule <path-to-input-file>β The path (absolute or relative) to the (CSV) input file that describes the network/schedule (flight-period) details π-o,--ond <path-to-input-file>β The path (absolute or relative) to the (CSV) input file with the O&D (origin/destination) details π-y,--yield <path-to-input-file>β The path (absolute or relative) to the (CSV) input file with the yield rule details π₯-t,--protocol <server network protocol>β The server protocol π«Ά-a,--address <server host address>β The server address πΈ-p,--port <server host port>β The server port π-l,--log <path-to-output-log-file>β The path (absolute or relative) to the output log file π
Want the defaults? Run AirInv --help and it'll show you all the default options. No cap, that's the move π
β¨ SEE ALSO β¨
Your next reading list, bestie π: airinv(1), AirInvClient(1), airinv-config(1), airinv-library(3) π§
β¨ SUPPORT β¨
Found a bug? Report it! Send it to https://sourceforge.net/apps/trac/airinv/report π
β¨ COPYRIGHT β¨
Copyright Β© 2009-2011 Denis Arnaud π
For more on the (LGPLv2+) license, check the COPYING file, or read it online at http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html β
Okay that's the whole page, bestie π«Ά Shoutout to My Project for the source, and to AirInvServer(1) for being an absolute main character ππ
π¦ where this page comes from
- fedora 44: airinv 1.00.15-1.fc44 Β· LGPL-2.1-or-later
- fedora 44: airinv 1.00.15-1.fc44 Β· LGPL-2.1-or-later
- π girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms