AMSSTOP(1)

πŸ“¦ version 3.2.1, in ubuntu jammy

πŸ’– AMSSTOP(1) πŸ’– AMS executables

✨ NAME ✨

okay bestie, amsstop is the Asynchronous Message Service (AMS) message space shutdown utility πŸ›‘πŸ’…

πŸŽ€ SYNOPSIS πŸŽ€

amsstop application_name authority_name

πŸ¦‹ DESCRIPTION πŸ¦‹

so amsstop is a utility program that shuts down everything running in the message space 🧚 That's the part of the AMS venture you named that's running in the local continuum. It stops all the registrars and all the application modules together. ngl it's a whole clean sweep 🧹

If one of the amsd tasks acting as a registrar for this venture is also the configuration server for the local continuum, that configuration server gets terminated too πŸ’€

application_name and authority_name have to point to an AMS venture that's known to run in the local continuum. It needs to be listed in the MIB for the amsstop application module πŸ“œ

Heads up, bestie: amsstop can only shut a message space down if the subject "amsstop" is defined in the MIBs of all modules in that message space. No subject, no shutdown πŸ™…β€β™€οΈ

🌸 EXIT STATUS 🌸

  • "0" β€” amsstop terminated normally, slay ✨
  • "1" β€” an anomalous exit status 😭 It means amsstop couldn't register, so it failed to shut its message space down. Check the ion.log file to see what went wrong.

🧚 FILES 🧚

You need a MIB initialization file with the applicable default name in place for this to work πŸ“‚ Check out amsrc(5) and amsxml(5) for the deets 🫢

🌈 ENVIRONMENT 🌈

No environment variables apply here, so there's nothing to set up πŸ™Œ

πŸ”₯ DIAGNOSTICS πŸ”₯

These diagnostics may get written to the ion.log log file, so peek there if things go sideways πŸ‘€

πŸ™ˆ amsstop can't register.

This one means amsstop couldn't register. It might be because the "amsstop" role isn't defined in the MIB initialization file 🫠

πŸ’œ amsstop subject undefined.

This means amsstop couldn't stop the message space because the "amsstop" subject isn't defined in the MIB initialization file. Not it πŸ’€

πŸ“ amsstop can't publish 'amsstop' message.

This means amsstop couldn't publish a message on the subject 'amsstop'. The reason should be noted in the ion.log log file, so go check there πŸ”

πŸ› BUGS πŸ›

If you find a bug, report it to <ion-bugs@korgano.eecs.ohiou.edu> πŸ’Œ

πŸ‘‘ SEE ALSO πŸ‘‘

amsrc(5)


okay that's the whole tea β˜• Source: perl v5.24.1, dated 2016-07-07. Stay iconic, bestie πŸ¦‹πŸ’–

πŸ“¦ where this page comes from