To use a custom NTP server, enter its URL in the NETCONFIG_NTP_STATIC_SERVERS option of the /etc/sysconfig/network/config configuration file. You can add more servers, separated by commas.

The System Services WebYaST module manages both standard (defined in /etc/init.d) and non-standard (custom services. The list of custom services that are managed with this module is defined in the /etc/webyast/custom_services.yml configuration file. The list of all (both standard and custom) system services that are shown in the WebYaST user interface is defined in the /etc/webyast/filter_services.yml configuration file.

5.2.1. Defining Custom Services¶

For each custom service, add an entry to the /etc/webyast/custom_services.yml file using the following format :

 service_name: 
 shortdescription: short_description 
 description: description  
 start: "start_command" 
 stop: "stop_command" 
 status: "status_command" 

	The name of the service.
	An optional short description of the service (one line summary).
	An optional enhanced human-readable description of the service.
	The command to start the service.
	The command to stop the service.
	The command to get the service status.

Example 5.1. Example custom_services.yml File

collectd:
  shortdescription: Statistics Collection Daemon
  description: Statistics Collection Daemon for filling RRD Files
  start: "/usr/sbin/rccollectd start"
  stop: "/usr/sbin/rccollectd stop"
  status: "/usr/sbin/rccollectd status"

	custom_services.yml File Permissions
Note that the /etc/webyast/custom_services.yml file in this example should be writable only by root, because start, stop and status scripts defined here are called with root privileges.

  - service_name

services:
  - cron
  - my_own_service
  - nfs
  - cups

The initial system setup is a sequence of configuration dialogs provided by selected WebYaST modules. You can customize the sequence by removing modules from the sequence, changing the sequence order, or by adding new modules. The initial system setup sequence is defined in the configuration file /etc/webyast/basesystem.yml.

 steps: 
  - controller: language 
  - controller: eulas 
  - controller: administrator 
  - controller: network 
  - controller: systemtime 
  - controller: mail_settings 
  - controller: registration 
 

-controller: controller_name

With the WebYaST eulas module, you can configure which end user license agreements (EULAs) are displayed to the user during the initial system setup.

You can configure one or more EULAs to be displayed. The list of EULAs to be used is defined in the /etc/webyast/eulas.yml configuration file.

    licenses:
    - SLES-11
    - APPLIANCE
   

- EULA_name

where EULA_name is the name of the directory containing the text of the EULA. The full path to this directory is /usr/share/yastws/eulas/licenses/EULA_name/ .

The EULA_name directory must contain plain text files with the text of the respective EULA. The text files should be named according to the following pattern: license.locale.txt. If the file with an appropriate locale is not found, license.txt is used as a fallback.

licenses:
- EULA_name

touch /var/lib/yastws/eulas/accepted-licenses/EULA_name
chown yastws /var/lib/yastws/eulas/accepted-licenses/EULA_name

The system update and system health information in the Control Panel is regularly updated. The default update interval is 5 minutes. The interval can be set in the /etc/webyast/control_panel.yml configuration file.

The /etc/webyast/control_panel.yml file uses the following format (showing the default values):

 patch_status_timeout: 28800
 system_status_timeout: 300
 display_patch_status: true
 display_system_status: true
 appliance_label: My Appliance

The WebYaST Status module uses the collectd daemon to get the data. The daemon uses plug-ins to collect various types of status data. In the /etc/collectd.conf configuration file, you can configure which plug-ins are loaded.

You can create an icon linking to an arbitrary site (such as your own web interface) in the WebYaST control panel Configuration area.

To create such a link, create a file named shortcuts.yml in the top directory of any WebYaST plugin or YaST2 Webclient root directory. The shortcuts.yml should have the following structure:

main:
  icon: '/icons/custom-icon.png' 
  url: http://example.com 
  groups: [ System ] 
  title: Title 
 

Custom vendor configuration files such as basesystem.yml, filter_services.yml, custom_services.yml, eulas.yml, logs.yml, or control_panel.yml can be placed under the /etc/webyast/vendor subdirectory overriding the default settings provided with the WebYaST installation. Branding packages should install modified configuration files under this directory.