AMSD(1)

Okay bestie, welcome to AMS executables 🎀 This is the manual for amsd, so let's get into it ✨

✨ NAME ✨

amsd — AMS configuration server and/or registrar daemon 🦋

✨ SYNOPSIS ✨

amsd { @ | MIB_source_name } { . | @ | config_server_endpoint_spec }
[application_name authority_name registrar_unit_name]

✨ DESCRIPTION ✨

okay so amsd is a background "daemon" task 💅 It can act as an AMS "configuration server" in the local continuum, as an AMS "registrar" in a specified cell, or highkey both at once 👑

If you pass a MIB_source_name, it has to name a MIB initialization file in the right format for amsd. That's either amsrc(5) or amsxml(5), depending on whether -DNOEXPAT was set at compile time. If you don't have one, you need @ instead, and then the built-in default MIB gets loaded 🌸

If this amsd task is NOT going to be a configuration server, the second command-line argument has to be a . character. Otherwise it has to be @ or config_server_endpoint_spec 🧚 If you use @, the endpoint specification for the configuration server gets computed automatically as the default endpoint specification for the primary transport service, as noted in the MIB: "hostname:2357" ✨

If an AMS module is NOT going to run in a background thread for this daemon (which is what lets you shut it down with amsstop(1) and/or update the MIB at runtime with amsmib(1)), then either the last three command-line arguments must be left out, or the "amsd" role must not be defined in the MIB loaded for this daemon. Otherwise, the application_name and authority_name arguments are required, and the "amsd" role must be defined in the MIB 🙈

If this amsd task is NOT going to be a registrar, the last command-line argument has to be left out. Otherwise the last three command-line arguments are required, and they must identify a unit in an AMS venture for the indicated application and authority that is known to operate in the local continuum, as noted in the MIB. Also, the unit name for the "root unit" of a venture is the zero-length string "" 💜

✨ EXIT STATUS ✨

• "0" — amsd terminated without error 💖
• -1 — amsd terminated due to an anomaly noted in the ion.log file 💀 If the termination wasn't commanded, investigate and solve the problem identified in the log file, then restart amsd.

✨ FILES ✨

If a MIB source name is specified, a file with that exact name must be present. Otherwise, a MIB initialization file with the applicable default name (see amsrc(5)) must be present 📂

✨ ENVIRONMENT ✨

No environment variables apply 🌈

✨ DIAGNOSTICS ✨

The following diagnostics may be issued to the ion.log log file 😭

• amsd can't load MIB. — The MIB initialization file was missing, unreadable, or invalid.
• amsd can't start CS. — Configuration server initialization failed for reasons noted in the ion.log file.
• amsd can't start RS. — Registrar initialization failed for reasons noted in the ion.log file.

✨ BUGS ✨

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> 🙈

✨ SEE ALSO ✨

amsmib(1), amsstop(1), amsrc(5), amsxml(5) 🫶

---

And that's the tea 💅 This page is from perl v5.24.1, dated 2016-07-07, and it's giving "read it once, use it forever" energy 🍓 Periodt ✨