[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
The fmadm
utility is the preferred method of managing a FreeM installation, and will eventually replace all of the existing utilities.
Unlike the existing, legacy utilities, fmadm
presents a consistent, simple interface for all FreeM management tasks, and is namespace-aware.
This appendix will document each fmadm
facility as it is implemented, until all of the legacy utilities have been replaced.
The fmadm
utility’s functions all follow the below, consistent syntax:
usage: fmadm <action> <object> <namespace> [OPTIONS]
The action keyword can be one of the following:
Lists instances of object
Examines a single instance of object
Verifies the integrity of object
Compacts object
Repairs integrity problems in object
Creates an instance of object
Removes an instance of object
Imports an object
Exports an object
Creates a backup of object
Restores a backup of object
Migrates an instance of object from an older FreeM version to the current version
Edits an instance of object
The object keyword can be one of the following:
The FreeM LOCK
table.
Supported actions are list
and remove
.
The FreeM ZALLOCATE
table.
No actions yet implemented.
FreeM after-image journaling.
Supported actions are examine
and restore
.
The examine
action will dump the after-image journal entries for the selected namespace in human-readable format.
The restore
action will play after-image journals forward for the selected namespace.
FreeM namespaces (collections of M routines and globals).
No actions yet implemented.
The database files representing each FreeM global.
Supported actions are list
, examine
, remove
, and verify
.
An M routine, stored as a .m
file.
Supported actions are list
, examine
, remove
, import
, export
, backup
, and edit
.
A UNIX process representing an instance of the FreeM runtime.
Supported actions are list
and examine
.
[ << ] | [ < ] | [ Up ] | [ > ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
This document was generated on September 20, 2023 using texi2html 5.0.