6. Layer root¶
6.1. Overview¶
This is the root
layer of the MFSYSCOM module.
This layer mainly includes core libraries and utilities like :
layerapi2 library and utilities which manage the layer system
wrappers (
python2
,python3
,python
…)(and some other documented below)
The root
layer is loaded by default and does not depend on another layer. This
is the layer dependencies root.
6.2. Special focus on python wrappers¶
6.2.1. python2 wrapper¶
The python2
wrapper is available in ${MFEXT_HOME}/bin
. It executes
a python2 interpreter with following layers loaded :
python2_core@mfext
python2@mfext
(if installed)python2@mfcom
(if installed)python2@{current_module}
(if installed)
So, if you want to execute a python2 script without any question about currently loaded layers, this is the way to go.
For example:
#!/usr/bin/env python2
print "this code will be always executed in python2 environment"
print "(thanks to the above python2 shebang)"
or
python2 /path/to/a/python2/script.py
6.2.2. python3 wrapper¶
The python3
wrapper is available in ${MFEXT_HOME}/bin
. It executes
a python3 interpreter with following layers loaded :
python3_core@mfext
python3@mfext
(if installed)python3@mfcom
(if installed)python3@{current_module}
(if installed)
So, if you want to execute a python3 script without any question about currently loaded layers, this is the way to go.
For example:
#!/usr/bin/env python3
print("this code will be always executed in python3 environment")
print("(thanks to the above python3 shebang)")
or
python3 /path/to/a/python3/script.py
6.2.3. python wrapper¶
The python
wrapper is available in ${MFEXT_HOME}/bin
. It works exactly
as the two above wrappers. But the major python version is selected with
the METWORK_PYTHON_MODE
environment variable.
6.4. Utilities¶
6.4.1. mfsysmon.start¶
usage mfsysmon.start [NOINIT]
=> start the mfsysmon module
6.4.2. mfsysmon.stop¶
usage mfsysmon.start
=> stop the mfsysmon module
6.4.3. mfsysmon.status¶
usage mfsysmon.status
=> test the mfsysmon module
6.4.4. mfsysmon.init¶
usage: mfsysmon.init
=> (re)init your module (WARNING: can't drop some user provided datas)
6.4.5. mfsysmon_wrapper¶
usage: /opt/metwork-mfsysmon-0.8/bin/mfsysmon_wrapper COMMAND_TO_WRAP [COMMAND_ARG1] [COMMAND_ARG2] [...]
=> launch the given command within metwork/mfsysmon environnent
=> note: the current environnent is cleared before
=> (only MODULE_RUNTIME_SUFFIX, MODULE_RUNTIME_HOME and some standard env var (HOME, TERM, DISPLAY...)
are keeped intact)