8.1.1. Procedure – Configure services with the Text editor plugin

1. Select a configuration template.

   By default, there are some predefined configuration templates available, these are actually configuration file skeletons for the given services.

   

   Figure 8.1. Default templates for the Text editor plugin

   Unless you want to configure DNS or NTP services, select Text editor minimal template.

   The following configuration window appears.

   

   Figure 8.2. Configuration window for the Text editor plugin

2. Supply Text component name.

   This parameters sets a label for the component.

3. Give Component configuration file name.

   Component configuration file name refers to the actual configuration file on the host that you want to edit.

   It is most likely a file in /etc or in one of its subdirectories since this is the default location for configuration files.

4. Set Component init script.

   Component init script refers to the script file or a link to it that is used to start and stop a given service. Without providing this file you cannot start/stop the service from MC. These scripts are installed in /etc/init.d.

   Note
   MC automatically prepends the /etc/init.d prefix, just type the name of the script.

5. Click OK after setting the necessary parameters.

   The main window of MC reappears with an empty component pane. This is normal; before working with the desired configuration file it is possible to download the content from the selected host.

6. Download and edit content from the selected host.

   Use the following button in the button bar to download the file to MC:

   You can edit the configuration file.

7. Propagate the modifications to the firewall.

   The steps are identical to that of the other components: commit the edited file to MS and then upload it to the host. Finally, the service can be started/stopped/restarted or reloaded the usual way.