[MAT logo][Prev][Up][Next]

Command-line options

Module command-line options

The MatPLC library recognises the following command-options. Individual modules may have additional options, which are documented in the relevant sections.
supplied by
--PLCplc_id= (integer) PLC id; if there is more than one MatPLC running, specifies which one to connect to. This is used as a shared memory key.
matplc, based on FIXME
--PLClocal Do not allocate a gmm private map; instead, do all operations directly on the global map. This is only really safe if synch is used to enforce serial execution of all modules, but can save memory copying. Also, the semantics of point ownership pretty much disappear.
manually in matplc.conf
--PLCisolate Separate the gmm global map into its own process, so that the rest of the module can't clobber it through stray pointers and the like. There is additional communication overhead.
manually in matplc.conf
--PLCshared (default) Allocate a gmm private map as usual.
manually in matplc.conf
--PLClocal_map_key= In the PLCisolate mode, optionally specifies the shared memory key. The default is to use a random one.
manually in matplc.conf
--PLCdebug= Specify the log level.
manually or in matplc.conf
--PLClogfile= Log file. Currently all messages (trace, warning and error) go to the one file.
matplc, based on FIXME
--PLCconf= Location of the matplc.conf file.
matplc, based on FIXME
--PLCmodule= name of the module
matplc, based on the first column in the module table
--PLCforce-init Start the module even if another module of the same name seems to be running. This can happen if the module exits without cleaning up and the PID is re-used, which should be fairly rare.
only when manually starting a module (makes no sense in matplc.conf)