LTS

    Innovation Version

      Basic Configuration

      Setting the System Locale

      System locale settings are stored in the /etc/locale.conf file and can be modified by the localectl command. These settings are read at system boot by the systemd daemon.

      Displaying the Current Locale Status

      To display the current locale status, run the following command:

      localectl status
      

      Example command output:

      $ localectl status
         System Locale: LANG=zh_CN.UTF-8
             VC Keymap: cn
            X11 Layout: cn
      

      Listing Available Locales

      To display available locales, run the following command:

      localectl list-locales
      

      You can check that by listing all Chinese locales with the following command:

      $ localectl list-locales | grep zh
      zh_CN.UTF-8
      

      Setting the Locale

      To set the language environment, run the following command as the user root. In the command, locale indicates the language type to be set. Run the localectl list-locales command to obtain the value range. Change the value as required.

      localectl set-locale LANG=locale
      

      For example, if you want to use Simplified Chinese as the locale, run the following command as the user root:

      localectl set-locale LANG=zh_CN.UTF-8
      

      NOTE:

      After the modification, log in again or run the command source /etc/locale.conf as the user root to update the configuration file for the modification to take effect:

      Setting the Keyboard Layout

      Keyboard layout settings are stored in the /etc/locale.conf file and can be modified by the localectl command. These settings are read at early boot by the systemd daemon.

      Displaying the Current Settings

      To display the current keyboard layout settings, run the following command:

      localectl status
      

      Example command output:

      $ localectl status
         System Locale: LANG=zh_CN.UTF-8
             VC Keymap: cn
            X11 Layout: cn
      

      Listing Available Keyboard Layouts

      To list all available keyboard layouts that can be configured on openEuler, run the following command:

      localectl list-keymaps
      

      For example, the command output of the Chinese keyboard layout is as follows:

      $ localectl list-keymaps | grep cn
      cn
      

      Setting the Keyboard Layout

      To set the keyboard layout, run the following command as the user root. In the command, map indicates the keyboard layout to be set. Run the localectl list-keymaps command to obtain the value range. Change it as required.

      localectl set-keymap map
      

      The keyboard layout will be equally applied to graphical user interfaces.

      Then you can verify if your setting was successful by checking the status:

      $ localectl status
         System Locale: LANG=zh_CN.UTF-8
             VC Keymap: cn
            X11 Layout: us
      

      Setting the Date and Time

      This topic describes how to set the system date, time, and time zone by using timedatectl, date, and hwclock commands.

      Using the timedatectl Command

      Displaying the Current Date and Time

      To display the current date and time, run the following command:

      timedatectl
      

      Example command output:

      $ timedatectl
                     Local time: Mon 2019-09-30 04:05:00 EDT
                 Universal time: Mon 2019-09-30 08:05:00 UTC
                       RTC time: Mon 2019-09-30 08:05:00
                      Time zone: China Standard Time (CST), UTC +8
      System clock synchronized: no
                    NTP service: inactive
                RTC in local TZ: no
      

      Synchronizing the System Clock with a Remote Server

      Your system clock can be automatically synchronized with a remote server using the Network Time Protocol (NTP). Run the following command as the user root to enable or disable NTP. The value of boolean is yes or no, indicating that the NTP is enabled or disabled for automatic system clock synchronization. Change the value as required.

      NOTE:
      If the remote NTP server is enabled to automatically synchronize the system clock, you cannot manually change the date and time. If you need to manually change the date or time, ensure that automatic NTP system clock synchronization is disabled. You can run the timedatectl set-ntp no command to disable the NTP service.

      timedatectl set-ntp boolean
      

      For example, to enable automatic remote time synchronization, run the following command:

      timedatectl set-ntp yes
      

      Changing the Current Date

      NOTE:
      Before changing the date, ensure that automatic NTP system clock synchronization has been disabled.

      Run the following command as the user root to change the current date. In the command, YYYY indicates the year, MM indicates the month, and DD indicates the day. Change them as required.

      timedatectl set-time YYYY-MM-DD
      

      For example, to change the current date to August 14, 2019, run the following command as the user root:

      timedatectl set-time '2019-08-14'
      

      Changing the Current Time

      NOTE:
      Before changing the time, ensure that automatic NTP system clock synchronization has been disabled.

      To change the current time, run the following command as the user root. In the command, HH indicates the hour, MM indicates the minute, and SS indicates the second. Change them as required.

      timedatectl set-time HH:MM:SS
      

      For example, to change the current time to 15:57:24, run the following command:

      timedatectl set-time 15:57:24
      

      Changing the Time Zone

      To list all available time zones, run the following command:

      timedatectl list-timezones
      

      To change the current time zone, run the following command as the user root. In the command, time_zone indicates the time zone to be set. Change it as required.

      timedatectl set-timezone time_zone
      

      Imagine you want to identify which time zone is closest to your present location while you are in Asia. You can check that by listing all available time zones in Asia with the following command:

      $ timedatectl list-timezones | grep Asia
      Asia/Aden
      Asia/Almaty
      Asia/Amman
      Asia/Anadyr
      Asia/Aqtau
      Asia/Aqtobe
      Asia/Ashgabat
      Asia/Baghdad
      Asia/Bahrain
      ......
      
      Asia/Seoul
      Asia/Shanghai
      Asia/Singapore
      Asia/Srednekolymsk
      Asia/Taipei
      Asia/Tashkent
      Asia/Tbilisi
      Asia/Tehran
      Asia/Thimphu
      Asia/Tokyo
      

      To change the time zone to Asia/Shanghai, run the following command:

      timedatectl set-timezone Asia/Shanghai
      

      Using the date Command

      Displaying the Current Date and Time

      To display the current date and time, run the following command:

      date
      

      By default, the date command displays the local time. To display the time in Coordinated Universal Time (UTC), run the command with the --utc or -u command line option:

      date --utc
      

      You can also customize the format of the displayed information by providing the + "format" option on the command line:

      date +"format"
      

      Table 1 Formatting options

      Format OptionDescription
      %HThe hour in the HH format (for example, 17)
      %MThe minute in the MM format (for example, 37)
      %SThe second in the SS format (for example, 25)
      %dThe day of the month in the DD format (for example, 15)
      %mThe month in the MM format (for example, 07)
      %YThe year in the YYYY format (for example, 2019)
      %ZThe time zone abbreviation (for example, CEST)
      %FThe full date in the YYYY-MM-DD format (for example, 2019-7-15). This option is equal to %Y-%m-%d
      %TThe full time in the HH:MM:SS format (for example, 18:30:25). This option is equal to %H:%M:%S

      Example commands and outputs:

      • To display the current date and time:

        $ date 
        Sat Aug  17 17:26:34 CST 2019
        
      • To display the current date and time in UTC:

        $ date --utc
        Sat Aug  17 09:26:18 UTC 2019
        
      • To customize the output of the date command:

        $ date +"%Y-%m-%d %H:%M"
        2019-08-17 17:24
        

      Changing the Current Time

      To change the current time, run the date command with the --set or -s option as the root user: Run the following command as the user root. In the command, HH indicates the hour, MM indicates the minute, and SS indicates the second. Change them as required.

      date --set HH:MM:SS
      

      By default, the date command sets the local time. To set the system clock in UTC instead, run the command with the --utc or -u command line option:

      date --set HH:MM:SS --utc
      

      For example, to change the current time to 23:26:00, run the following command as the user root:

      date --set 23:26:00
      

      Changing the Current Date

      To change the current date, run the command with the --set or -s command line option. Run the following command as the user root. In the command, YYYY indicates the year, MM indicates the month, and DD indicates the day. Change them as required.

      date --set YYYY-MM-DD
      

      For example, to change the current date to November 2, 2019, run the following command as the user root:

      date --set 2019-11-02
      

      Using the hwclock Command

      You can run the hwclock command to set the real time clock (RTC).

      Real-Time Clock and System Clock

      Linux divides clocks into the following types:

      • System clock: clock of the current Linux kernel.
      • Hardware clock RTC: hardware clock of the mainboard powered by the battery. This clock can be set in the Standard BIOS Feature option of the BIOS.

      When Linux starts, it reads the RTC and sets the system clock time based on the RTC time.

      Displaying the Current Date and Time

      To display the current RTC date and time, run the following command as the user root:

      hwclock
      

      Example command output:

      $ hwclock
      2019-08-26 10:18:42.528948+08:00
      

      Setting the Date and Time

      Run the following command as the user root to change the date and time of the current hardware. In the command, dd indicates the day, mm indicates the month, yyyy indicates the year, HH indicates the hour, and MM indicates the minute. Change them as required.

      hwclock --set --date "dd mm yyyy HH:MM"
      

      For example, to change the current time to 21:17 on October 21, 2019, run the following command:

      hwclock --set --date "21 Oct 2019 21:17" --utc
      

      Setting kdump

      This section describes how to set the memory reserved for kdump and modify parameters in the kdump configuration file.

      Setting the Memory Reserved for kdump

      Parameter Formats of the Memory Reserved for kdump

      The memory reserved for kdump must be added to the bootargs in the /boot/efi/EFI/openEuler/grub.cfg configuration file. The memory reserved for kdump has been added to the released openEuler version by default and can be adjusted as required. After adding or modifying the bootargs, restart the system for the setting to take effect. The parameter formats of the memory reserved for kdump are as follows:

      BootargDescriptionDefault ValueRemarks
      crashkernel=xIf the physical memory size is less than 4 GB, x of the memory is reserved for kdump.The default value is 512 MB for x86.This configuration method is used only when the available memory size is less than 4 GB. In this case, ensure that the available contiguous memory is sufficient for reservation.
      crashkernel=x@yx of the memory is reserved at the start address of y for kdump.UnusedEnsure that x of the memory at the start address of y is not reserved for other modules.
      crashkernel=x,highIf the physical memory size is less than 4 GB, 256 MB memory is reserved. If the physical memory size is greater than 4 GB, x of the memory is reserved for kdump.The default value is 1024M,high for ARM64.Ensure that the available physical contiguous memory size is greater than or equal to 256 MB when the memory size is less than 4 GB, and is greater than or equal to x when the memory size is greater than 4 GB. The actual reserved memory size is 256 MB + x.
      crashkernel=x,low crashkernel=y,highx of the memory is reserved for kdump when the physical memory size is less than 4 GB, and y of the memory is reserved for kdump when the physical memory size is greater than 4 GB.UnusedEnsure that the available physical contiguous memory size is greater than or equal to x when the physical memory size is less than 4 GB, and is greater than or equal to y when the physical memory size is greater than 4 GB.
      Recommended SolutionReserved ParameterDescription
      General solutioncrashkernel=2048M,highIf the memory size is less than 4 GB, 256 MB is reserved for kdump. If the memory size is greater than 4 GB, 2048 MB is reserved for kdump. 256 + 2048 MB in total.
      Economical solutioncrashkernel=1024M,highIf the memory size is less than 4 GB, 256 MB is reserved for kdump. If the memory size is greater than 4 GB, 1024 MB is reserved for kdump. 256 + 1024 MB in total. It is recommended that kdump files not be dumped using the network in scenarios where the system memory size is less than 512 GB. In VM scenarios, you can reduce the reserved memory. You are advised to set crashkernel to 512M or crashkernel to 256M,high.

      NOTE:

      If kdump files are not dumped using the network, you need to set the kdump file system not to pack network drivers. Loading the network driver requires a large amount of memory. As a result, the memory reserved for kdump may be insufficient and kdump may fail. Therefore, you are advised to disable network drivers.

      Disabling Network Drivers

      In the kdump configuration file /etc/kdump.conf, the dracut parameters can be used to set the tailored driver module. You can configure the network driver to the tailored driver list to prevent the kdump file system from loading the driver. After the configuration file is modified, restart the kdump service for the modification to take effect. Set the dracut parameters as follows:

      dracut_args --omit-drivers "mdio-gpi usb_8dev et1011c rt2x00usb bcm-phy-lib mac80211_hwsim rtl8723be rndis_host hns3_cae amd vrf rtl8192cu mt76x02-lib int51x1 ppp_deflate team_mode_loadbalance smsc911x aweth bonding mwifiex_usb hnae dnet rt2x00pci vaser_pci hdlc_ppp marvell rtl8xxxu mlxsw_i2c ath9k_htc rtl8150 smc91x cortina at803x rockchip cxgb4 spi_ks8995 mt76x2u smsc9420 mdio-cavium bnxt_en ch9200 dummy macsec ice mt7601u rtl8188ee ixgbevf net1080 liquidio_vf be2net mlxsw_switchx2 gl620a xilinx_gmii2rgmii ppp_generic rtl8192de sja1000_platform ath10k_core cc770_platform realte igb c_can_platform c_can ethoc dm9601 smsc95xx lg-vl600 ifb enic ath9 mdio-octeon ppp_mppe ath10k_pci cc770 team_mode_activebackup marvell10g hinic rt2x00lib mlx4_en iavf broadcom igc c_can_pci alx rtl8192se rtl8723ae microchip lan78xx atl1c rtl8192c-common almia ax88179_178a qed netxen_nic brcmsmac rt2800usb e1000 qla3xxx mdio-bitbang qsemi mdio-mscc-miim plx_pci ipvlan r8152 cx82310_eth slhc mt76x02-usb ems_pci xen-netfront usbnet pppoe mlxsw_minimal mlxsw_spectrum cdc_ncm rt2800lib rtl_usb hnae3 ath9k_common ath9k_hw catc mt76 hns_enet_drv ppp_async huawei_cdc_ncm i40e rtl8192ce dl2 qmi_wwan mii peak_usb plusb can-dev slcan amd-xgbe team_mode_roundrobin ste10Xp thunder_xcv pptp thunder_bgx ixgbe davicom icplus tap tun smsc75xx smsc dlci hns_dsaf mlxsw_core rt2800mmi softing uPD60620 vaser_usb dp83867 brcmfmac mwifiex_pcie mlx4_core micrel team macvlan bnx2 virtio_net rtl_pci zaurus hns_mdi libcxgb hv_netvsc nicvf mt76x0u teranetics mlxfw cdc_eem qcom-emac pppox mt76-usb sierra_net i40evf bcm87xx mwifiex pegasus rt2x00mmi sja1000 ena hclgevf cnic cxgb4vf ppp_synctty iwlmvm team_mode_broadcast vxlan vsockmon hdlc_cisc rtl8723-common bsd_comp fakelb dp83822 dp83tc811 cicada fm10 8139t sfc hs geneve hclge xgene-enet-v2 cdc_mbim hdlc asix netdevsim rt2800pci team_mode_random lxt ems_usb mlxsw_pci sr9700 mdio-thunder mlxsw_switchib macvtap atlantic cdc_ether mcs7830 nicpf mdi peak_pci atl1e cdc_subset ipvtap btcoexist mt76x0-common veth slip iwldvm bcm7xxx vitesse netconsole epic100 myri10ge r8169 qede microchip_t1 liquidi bnx2x brcmutil mwifiex_sdi mlx5_core rtlwifi vmxnet3 nlmon hns3 hdlc_raw esd_usb2 atl2 mt76x2-common iwlwifi mdio-bcm-unimac national ath rtwpci rtw88 nfp rtl8821ae fjes thunderbolt-net 8139cp atl1 mscc vcan dp83848 dp83640 hdlc_fr e1000e ipheth net_failover aquantia rtl8192ee igbvf rocker intel-xway tg3" --omit "ramdisk network ifcfg qemu-net" --install "chmod" --nofscks

      Setting the Disk Scheduling Algorithm

      This section describes how to set the disk scheduling algorithm.

      Temporarily Modifying the Scheduling Policy

      For example, if all I/O scheduling algorithms are changed to mq-deadline, the modification becomes invalid after the system is restarted.

      echo mq-deadline > /sys/block/sd*/queue/scheduler
      

      Permanently Setting the Scheduling Policy

      You can add elevator=mq-deadline to the kernel line in the kernel boot configuration file grub.cfg. The setting takes effect after the system is restarted.

      linux   /vmlinuz-4.19.90-2003.4.0.0036.oe1.x86_64 root=/dev/mapper/openeuler-root ro resume=/dev/mapper/openeuler-swap rd.lvm.lv=openeuler/root rd.lvm.lv=openeuler/swap quiet crashkernel=512M elevator=mq-deadline
      

      Setting the NMI Watchdog

      The non-maskable interrupt (NMI) is the highest priority interrupt in the system. The NMI watchdog can be used to detect server suspension events and trigger the server reboot after fault information is collected. According to the lab test results of the openEuler QA team, when the NMI watchdog is enabled, NMI occasionally generates a large number of interrupts and deteriorates the server performance. Therefore, properly enable the NMI watchdog function.

      Note: The following NMI watchdog settings apply only to hardware servers whose compatibility has been verified by the openEuler community. For other types of servers and VMs, the NMI watchdog settings are for reference only.

      1. Run the following command to display the current NMI watchdog configuration status:

        $ sudo sysctl kernel.nmi_watchdog 
        kernel.nmi_watchdog = 0 
        
      2. Run the following command to set the NMI watchdog parameters:

        sudo sysctl  -w kernel.nmi_watchdog=1
        

        Value 1: enabled; Value 0: disabled

      3. Run the following command to display the kernel log print level:

        $ sysctl kernel.printk
        kernel.printk = 4      4      1      7
        

        To change the kernel log print level, modify /etc/sysctl.d/21-openEuler.conf and run the following command:

        sysctl -p /etc/sysctl.d/21-openEuler.conf
        

      Bug Catching

      Buggy Content

      Bug Description

      Submit As Issue

      It's a little complicated....

      I'd like to ask someone.

      PR

      Just a small problem.

      I can fix it online!

      Bug Type
      Specifications and Common Mistakes

      ● Misspellings or punctuation mistakes;

      ● Incorrect links, empty cells, or wrong formats;

      ● Chinese characters in English context;

      ● Minor inconsistencies between the UI and descriptions;

      ● Low writing fluency that does not affect understanding;

      ● Incorrect version numbers, including software package names and version numbers on the UI.

      Usability

      ● Incorrect or missing key steps;

      ● Missing prerequisites or precautions;

      ● Ambiguous figures, tables, or texts;

      ● Unclear logic, such as missing classifications, items, and steps.

      Correctness

      ● Technical principles, function descriptions, or specifications inconsistent with those of the software;

      ● Incorrect schematic or architecture diagrams;

      ● Incorrect commands or command parameters;

      ● Incorrect code;

      ● Commands inconsistent with the functions;

      ● Wrong screenshots.

      Risk Warnings

      ● Lack of risk warnings for operations that may damage the system or important data.

      Content Compliance

      ● Contents that may violate applicable laws and regulations or geo-cultural context-sensitive words and expressions;

      ● Copyright infringement.

      How satisfied are you with this document

      Not satisfied at all
      Very satisfied
      Submit
      Click to create an issue. An issue template will be automatically generated based on your feedback.
      Bug Catching
      编组 3备份