When you are going to make changes to the Opmantek application configuration, you should exercise caution as the files are a structured file like JSON which is actually a Perl data structure. In more recent versions of Opmantek Software we have moved to JSON configuration files.
| Table of Contents |
|---|
Before editing
Before editing the file, make a backup, e.g.
| Code Block |
|---|
cp /usr/local/omk/conf/opCommon.nmis /usr/local/omk/conf/opCommon.nmis.backup.$USER.$PPID |
Using .$USER.$PID, provides a simple unique identifier for getting backups, datestamps are good too, but this is quick and easily repeated for restoration.
After editing
After editing the file, verify the syntax with the following command
| Code Block |
|---|
perl -c /usr/local/omk/conf/opCommon.nmis |
In case of Error
If you get an error message like the following:
...
First carefully read the message, this example is quite common, all that is required is to add a comma to the end of the line, but if you can not understand the issue, restore your backup.
Restore your backup
| Code Block |
|---|
cp /usr/local/omk/conf/opCommon.nmis /usr/local/omk/conf/opCommon.nmis.bad.$USER.$PPID cp /usr/local/omk/conf/opCommon.nmis.backup.$USER.$PPID |
...
/usr/local/omk/conf/opCommon.nmis |
Restart the daemon
Most changes to opCommon.nmis will require the daemon to be restarted.
| Code Block |
|---|
sudo service omkd restart |
Other daemons may need to be restarted, for examples see below, typically GUI features require omkd to be restarted and application features required the daemon to be restarted.
| Application Configuration | Daemon | Command to run |
|---|---|---|
| opEvents | opeventsd | sudo service opeventsd restart |
| opCharts | opchartsd | sudo service opchartsd restart |
| opConfig | opconfigd | sudo service opconfigd restart |
| opFlow or opFlowSP | opflowd | sudo service opflowd restart |
| opTrend | optrend | sudo service optrendd restart |