AMSLOG(1)

๐Ÿ“ฆ version 3.2.1, in ubuntu jammy

Okay bestie, welcome to the amslog manual ๐Ÿฆ‹ It's part of the AMS executables crew, and by the end you'll see why it's giving main character energy ๐Ÿ’…

โœจ NAME โœจ

amslog โ€” the Asynchronous Message Service (AMS) test message receiver ๐Ÿ“จ


๐Ÿ’œ SYNOPSIS ๐Ÿ’œ

amslog unit_name role_name application_name authority_name [{ s | i }]

๐ŸŒธ DESCRIPTION ๐ŸŒธ

So amslog is a message receiver, and its whole purpose in life is helping you test AMS functionality ๐Ÿงช literally built for it ๐Ÿซถ

When you start amslog, it registers itself as an application module. It signs up in the unit called unit_name, inside the venture called application_name under authority_name, and it registers in the role you give it as role_name ๐ŸŽ€. Quick heads-up: for this to work, a configuration server for the local continuum AND a registrar for that unit of that venture need to be running first โœจ. They can both live in one amsd daemon task, which is lowkey neat ๐Ÿงš

Under the hood it runs two threads ๐Ÿงต. The background thread catches incoming AMS messages and logs them to standard output. The foreground thread reads lines of console input, and those lines are how you control which messages reach the background thread ๐Ÿ‘‘

Here are the foreground thread's rules, so pay attention bestie ๐Ÿ‘€

  • If the very first character of a line from stdin is . (period), amslog terminates immediately ๐Ÿ’€ bye bye.
  • Otherwise, the first character has to be + (you're asserting interest in a subject) or - (you're cancelling that interest) ๐Ÿ’….
  • The subject name starts at the second character of the line.
  • everything is a totally valid subject name, so yes, you can go full send ๐ŸŒˆ.

By default amslog runs in subscribe mode ๐Ÿ“ฎ. When you assert interest, it subscribes to that subject, and when you rescind interest, it unsubscribes from it. You can switch the vibe by giving a third command-line argument, the mode indicator. Pass i and it switches to invite mode ๐Ÿ“. In invite mode, asserting interest means it invites messages on that subject, and rescinding means it cancels that invitation.

Want to get specific about where your subscription or invitation applies? You can add a domain right after the subject name, on the same line of console input โœจ

  • The domain continuum name can be specified, or you can use the placeholder _ to mean "all continua" ๐ŸŒ.
  • If a domain continuum name is given (either _ or an actual name), you can then specify a domain unit name, or use _ to mean "the root unit," aka the entire venture ๐Ÿ‘‘.
  • If a domain unit name is given (either _ or an actual name), you can then specify a domain role name too ๐ŸŽ€.

Now for output ๐Ÿ–จ๏ธ. On VxWorks or RTEMS, each message's subject and content just get written to standard output as a text line so you can read them on the console ๐Ÿ“บ. On UNIX, it's a different situation: the subject name length (a binary integer), subject name (ASCII text), content length (a binary integer), and content (ASCII text) all get written to standard output. That means you redirect it into a file, or pipe it into amslogprt ๐Ÿ”ฅ.

One more thing, and it's iconic ๐Ÿ’… whenever a message comes in flagged as a Query, amslog sends back a reply. The reply's content is the string Got followed by the first 128 bytes of the Query's content, wrapped in single quote marks, and then a period at the end ๐Ÿซถ.


๐Ÿฆ‹ EXIT STATUS ๐Ÿฆ‹

  • -1 โ€” amslog terminated with an error, as noted in the ion.log file ๐Ÿ˜ญ.
  • "0" โ€” amslog terminated normally โœจ.

๐Ÿ“ FILES ๐Ÿ“

A MIB initialization file with the applicable default name must be present. Check amsrc(5) for the deets ๐Ÿ“š.

๐ŸŒ ENVIRONMENT ๐ŸŒ

No environment variables apply ๐Ÿ™Œ zero env vars, zero drama.

๐Ÿšจ DIAGNOSTICS ๐Ÿšจ

Error messages are the tea of this program ๐Ÿต

  • amslog can't register. โ€” amslog failed to register, for reasons noted in the ion.log file.
  • amslog can't set event manager. โ€” amslog failed to start its background thread, for reasons noted in the ion.log file.
  • amslog can't read from stdin โ€” the foreground thread failed to read console input, for reasons noted in the ion.log file.

๐Ÿ› BUGS ๐Ÿ›

Found a bug? Report it to <ion-bugs@korgano.eecs.ohiou.edu> ๐Ÿž

๐Ÿ‘ฏ SEE ALSO ๐Ÿ‘ฏ

amsshell(1), amslogprt(1), amsrc(5) ๐Ÿ’–


That's the whole tea, bestie ๐Ÿซถ This page came from perl v5.24.1, dated 2016-07-07, and it's all AMSLOG(1) all the way down ๐ŸŒธ love u, mwah ๐Ÿ’‹

๐Ÿ“ฆ where this page comes from