我们有 SUSE Linux 系统，我们有各种分区，我们正面临 FS 的损坏。我们现在尝试在不重新启动系统的情况下定期扫描 FS，我们已经通过 fsck 选项，但在手册页上我们知道我们无法使用，因为结果在已安装的分区上不可靠。因此，有人可以帮助我使用任何方法来扫描已安装的文件系统，从而避免系统重新启动。
Micro Focus Data Protector 10.91 应该与使用 systemd 的 SLES 等 Linux 发行版一起使用，但客户端安装似乎不起作用：当我尝试安装客户端时，我收到一条错误消息（“ [110:101] 客户端导入失败！ ”）而之前的安装步骤（核心组件、核心技术堆栈、磁盘代理）看起来很成功。
检查系统时，我看到有一个omni.socket服务在运行，但引用的omni.service不存在（没有对应的单元文件）。经过仔细检查，我发现了一个[email protected]in /usr/lib/systemd/system/，但这似乎无效。
我能做些什么来解决这个问题？
服务文件如下所示：
# /usr/lib/systemd/system/omni.socket
[Unit]
Description=DATA-PROTECTOR-INET
PartOf=omni.service
[Socket]
ListenStream=5555
Accept=yes
MaxConnections=1000000
MaxConnectionsPerSource=100000
[Install]
WantedBy=sockets.target
# /usr/lib/systemd/system/[email protected]
[Unit]
Description=DATA-PROTECTOR-INET
Requires=omni.socket
[Service]
StandardInput=socket
PIDFile=/var/run/omni.pid
ExecStart=/opt/omni/lbin/inet -log /var/opt/omni/log/inet.log
Type=simple
KillMode=process
[Install]
WantedBy=default.target
对我来说，这些服务文件似乎非常不完整：它们缺少网络和本地文件系统等依赖项。
澄清一下：我不是在寻找产品已经提供的安装说明（它们不起作用）。相反，我正在寻找一种在供应商修复错误时使错误版本工作的方法。
我需要使用需要选择解决方案的 zypper 自动安装包。如何在非交互模式下完成？
# zypper in /tmp/repos-sles15-sp2-current.x86_64.rpm
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides sles-release = 15.2 needed by repos-sles15-sp2-x86_64-20210609-1.x86_64
Solution 1: do not install repos-sles15-sp2-x86_64-20210609-1.x86_64
Solution 2: break repos-sles15-sp2-x86_64-20210609-1.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c/d/?] (c): c
我需要选择选项#2。我试过的：
- 回声 2 | /tmp/repos-sles15-sp2-current.x86_64.rpm 中的 zypper
- 是 2 | /tmp/repos-sles15-sp2-current.x86_64.rpm 中的 zypper
- zypper 在 /tmp/repos-sles15-sp2-current.x86_64.rpm --force -y
有谁知道有助于选择选项＃2的技巧？
我运行这些命令在 openSUSE Tumbleweed 上安装 DNS 服务器依赖项：
sudo zypper in -t pattern dhcp_dns_server
sudo systemctl enable named.service
sudo systemctl start named.service
要配置 DNS 服务器，我正在按照本文档尝试 YAST2 ：
sudo yast2 dns-server
我打算example.com用 IP 地址配置域区域1.2.3.4。
我做了什么
我有一个主类型的 DNS 区域：
我的NS 记录选项卡是：
我的记录选项卡是：
问题
但是，保存配置会遇到问题：
警告
保存配置失败。更改设置？
我想不通。任何人都可以帮忙吗？
更新
由@JiriB 建议，我运行了这些命令并重新配置了 DNS 服务器。但观察结果和之前一样：
sudo systemctl revert named.service
sudo rpm -qV bind
sudo cp /etc/named.conf.YaST-backup /etc/named.conf
sudo yast2 dns-server
我正在尝试通过 SSH 从 Windows 10 计算机连接到远程 SUSE Linux Enterprise Server 11。
使用 Putty 0,73 时，它可以正常工作。但是使用 WSL2/Debian 我总是被拒绝。
在 Linux 机器上，当我打开/var/log/messages文件时，每次尝试使用 WSL2 访问时都会看到以下行：
2 月 8 日 12:46:31 远程计算机名 sshd [13536]：致命：buffer_put_cstring：s == NULL [preauth]
在 WSL 上，我只是收到一个连接关闭错误：
$ ssh root@ip-of-remote-linux
Connection closed by ip-of-remote-linux port 22
任何想法两台计算机之间的问题是什么？
在 SLES 12 虚拟机上，该命令rpm -qa不会向标准输出返回任何内容。
~> rpm -qa
~>
该命令在 1 或 2 秒后完成，因此它清楚地生成了一些数据。只有当输出被重定向到文件或通过管道时，它才会变得可见：
~> rpm -qa > out.txt # works fine
~> rpm -qa | grep lib
libgcc ...
...
问题不在于 rpm 数据库，其中的数据库文件/var/lib/rpm/存在并且看起来很健康，此处建议的重建并不能解决问题。
我只有一个从 SLES 11 升级的普通 SLES 12 VM。我想将它升级到 SLES 15，我没有任何新模块，如 HPC、SAP 等。只是普通 SLES。我如何知道在升级过程中我需要选择哪些附加产品？
我的 /etc/resolv.conf：
### /etc/resolv.conf file autogenerated by netconfig!
#
# Before you change this file manually, consider to define the
# static DNS configuration using the following variables in the
# /etc/sysconfig/network/config file:
# NETCONFIG_DNS_STATIC_SEARCHLIST
# NETCONFIG_DNS_STATIC_SERVERS
# NETCONFIG_DNS_FORWARDER
# or disable DNS configuration updates via netconfig by setting:
# NETCONFIG_DNS_POLICY=''
#
# See also the netconfig(8) manual page and other documentation.
#
# Note: Manual change of this file disables netconfig too, but
# may get lost when this file contains comments or empty lines
# only, the netconfig settings are same with settings in this
# file and in case of a "netconfig update -f" call.
#
### Please remove (at least) this line when you modify the file!
我检查了 /etc/sysconfig/network/config 中 NETCONFIG_DNS_STATIC_SERVERS 的值，这是正确的。
在 yast lan，主机名/DNS，修改 DNS 配置，它说“仅手动”，DNS 服务器列在“名称服务器和域搜索列表”下面是我的 /etc/sysconfig/network/config：
## Type: yesno
## Default: yes
# sometimes we want some script to be executed after an interface has been
# brought up, or before an interface is taken down.
# default dir is /etc/sysconfig/network/if-up.d for POST_UP and
# /etc/sysconfig/network/if-down.d for PRE_DOWN
# Note: if you use NetworkManager then down scripts will be called after the
# interface is down and not before.
GLOBAL_POST_UP_EXEC="yes"
GLOBAL_PRE_DOWN_EXEC="yes"
## Path: Network/General
## Description: Global network configuration
## Type: yesno
## Default: no
# If ifup should check if an ip address is already in use, set this to yes.
# Make sure that packet sockets (CONFIG_PACKET) are supported in the kernel,
# since this feature uses arping, which depends on that.
# Also be aware that this takes one second per interface; consider that when
# setting up a lot of interfaces.
CHECK_DUPLICATE_IP="no"
## Type: yesno
## Default: no
# Switch on/off debug messages for all network configuration stuff. If set to no
# most scripts can enable it locally with "-o debug".
DEBUG="no"
# Handling of network connections
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# These features are designed for the convenience of the experienced
# user. If you encounter problems you don't understand then switch
# them off. That is the default.
# Please do not complain if you get troubles. But if you want help to
# make them smarter write to <http://www.suse.de/feedback>.
## Type: yesno
## Default: no
#
# If you are interested in the connections and nfs mounts that use a
# network interface, you can set CONNECTION_SHOW_WHEN_IFSTATUS="yes".
# Then you will see them with 'ifstatus <interface>' (or 'ifstatus
# <config>')
# This one _should_ never harm ;)
#
CONNECTION_SHOW_WHEN_IFSTATUS="no"
## Type: yesno
## Default: no
#
# If an interface should be set down only if there are no active
# connections, then use CONNECTION_CHECK_BEFORE_IFDOWN="yes"
#
CONNECTION_CHECK_BEFORE_IFDOWN="no"
## Type: yesno
## Default: no
#
# If these connetions (without the nfs mounts) should be closed when
# shutting down an interface, set CONNECTION_CLOSE_BEFORE_IFDOWN="yes".
# WARNING: Be aware that this may terminate applications which need
# one of these connections!
#
CONNECTION_CLOSE_BEFORE_IFDOWN="no"
## Type: yesno
## Default: no
#
# If you are a mobile laptop user and like even nfs mounts to be
# closed when you leave your current workplace, then set
# CONNECTION_UMOUNT_NFS_BEFORE_IFDOWN="yes". This does only work
# if CONNECTION_CLOSE_BEFORE_IFDOWN="yes", too.
# WARNING: Be aware that this may terminate applications which use
# these nfs mounts as working directory. Be very carefull if your home
# is mounted via nfs!!!
# WARNING: This may even lead to hanging ifdown processes if there are
# processes that could not be terminated. If you are using
# hotpluggable devices (pcmcia, usb, firewire), first shut them down
# before unplugging!
#
CONNECTION_UMOUNT_NFS_BEFORE_IFDOWN="no"
## Type: yesno
## Default: no
#
# If terminating processes that use a connection or nfs mount is not
# enough, then they can be killed after an unsuccesfull termination.
# If you want that set CONNECTION_SEND_KILL_SIGNAL="yes"
#
CONNECTION_SEND_KILL_SIGNAL="no"
## Type: integer
## Default: 30
#
# Some interfaces need some time to come up or come asynchronously via hotplug.
# WAIT_FOR_INTERFACES is a global wait for all mandatory interfaces in
# seconds. If empty no wait occurs.
#
WAIT_FOR_INTERFACES="30"
## Type: yesno
## Default: yes
#
# With this variable you can determine if the SuSEfirewall when enabled
# should get started when network interfaces are started.
FIREWALL="yes"
## Type: int
## Default: 30
#
# When using NetworkManager you may define a timeout to wait for NetworkManager
# to connect in /etc/init.d/network(-remotefs) script. Other network services
# may require the system to have a valid network setup in order to succeed.
#
# This variable has no effect if NETWORKMANAGER=no.
#
NM_ONLINE_TIMEOUT="30"
## Type: string
## Default: "dns-resolver dns-bind ntp-runtime nis"
#
# This variable defines the start order of netconfig modules installed
# in the /etc/netconfig.d/ directory.
#
# To disable the execution of a module, don't remove it from the list
# but prepend it with a minus sign, "-ntp-runtime".
#
NETCONFIG_MODULES_ORDER="dns-resolver dns-bind dns-dnsmasq nis ntp-runtime"
## Type: string
## Default: "auto"
#
# Defines the DNS merge policy as documented in netconfig(8) manual page.
# Set to "" to disable DNS configuration.
#
NETCONFIG_DNS_POLICY=""
## Type: string(resolver,bind,dnsmasq,)
## Default: "resolver"
#
# Defines the name of the DNS forwarder that has to be configured.
# Currently implemented are "bind", "dnsmasq" and "resolver", that
# causes to write the name server IP addresses to /etc/resolv.conf
# only (no forwarder). Empty string defaults to "resolver".
#
NETCONFIG_DNS_FORWARDER="resolver"
## Type: string
## Default: ""
#
# List of DNS domain names used for host-name lookup.
# It is written as search list into the /etc/resolv.conf file.
#
NETCONFIG_DNS_STATIC_SEARCHLIST="test.com"
## Type: string
## Default: ""
#
# List of DNS nameserver IP addresses to use for host-name lookup.
# When the NETCONFIG_DNS_FORWARDER variable is set to "resolver",
# the name servers are written directly to /etc/resolv.conf.
# Otherwise, the nameserver are written into a forwarder specific
# configuration file and the /etc/resolv.conf does not contain any
# nameservers causing the glibc to use the name server on the local
# machine (the forwarder). See also netconfig(8) manual page.
#
NETCONFIG_DNS_STATIC_SERVERS="172.19.9.12 172.19.9.13 172.19.9.14"
## Type: string
## Default: "auto"
#
# Allows to specify a custom DNS service ranking list, that is which
# services provide preferred (e.g. vpn services), and which services
# fallback settings (e.g. avahi).
# Preferred service names have to be prepended with a "+", fallback
# service names with a "-" character. The special default value
# "auto" enables the current build-in service ranking list -- see the
# netconfig(8) manual page -- "none" or "" disables the ranking.
#
NETCONFIG_DNS_RANKING="auto"
## Type: string
## Default: "auto"
#
# Defines the NTP merge policy as documented in netconfig(8) manual page.
# Set to "" to disable NTP configuration.
#
NETCONFIG_NTP_POLICY="auto"
## Type: string
## Default: ""
#
# List of NTP servers.
#
NETCONFIG_NTP_STATIC_SERVERS=""
## Type: string
## Default: "auto"
#
# Defines the NIS merge policy as documented in netconfig(8) manual page.
# Set to "" to disable NIS configuration.
#
NETCONFIG_NIS_POLICY="auto"
## Type: string(yes,no,)
## Default: "yes"
#
# Defines whether to set the default NIS domain. When enabled and no domain
# is provided dynamically or in static settings, /etc/defaultdomain is used.
# Valid values are:
# - "no" or "" netconfig does not set the domainname
# - "yes" netconfig sets the domainname according to the
# NIS policy using settings provided by the first
# iterface and service that provided it.
# - "<interface name>" as yes, but only using settings from interface.
#
NETCONFIG_NIS_SETDOMAINNAME="yes"
## Type: string
## Default: ""
#
# Defines a default NIS domain.
#
# Further domain can be specified by adding a "_<number>" suffix to
# the NETCONFIG_NIS_STATIC_DOMAIN and NETCONFIG_NIS_STATIC_SERVERS
# variables, e.g.: NETCONFIG_NIS_STATIC_DOMAIN_1="second".
#
NETCONFIG_NIS_STATIC_DOMAIN=""
## Type: string
## Default: ""
#
# Defines a list of NIS servers for the default NIS domain or the
# domain specified with same "_<number>" suffix.
#
NETCONFIG_NIS_STATIC_SERVERS=""
## Type: yesno
## Default: yes
#
# When enabled (default) in forwarder mode ("bind", "dnsmasq"),
# netconfig writes an explicit localhost nameserver address to the
# /etc/resolv.conf, followed by the policy resolved name server list
# as fallback for the moments, when the local forwarder is stopped.
#
NETCONFIG_DNS_FORWARDER_FALLBACK="yes"
## Type: list(auto,yes,no)
## Default: auto
# If ifup should send a gratuitous ARP to inform the receivers about its
# static IP addresses and perhaps also a link-layer (MAC) address change.
# Make sure that packet sockets (CONFIG_PACKET) are supported in the kernel,
# since this feature uses arping, which depends on that.
SEND_GRATUITOUS_ARP="no"
## Type: integer
## Default: 0
#
# The number of seconds to wait for link to become useable / ready.
# Default is 0, causing to not wait for a ready link (0), because link
# detection can't be enabled in all cases (e.g. bridges without ports).
# Please use per interface settings to enable it.
#
LINK_READY_WAIT="0"
## Type: integer
## Default: ""
#
# The number of seconds to wait for the end of IPv6 duplicate address
# detection in ifup.
# Default is to use WAIT_FOR_INTERFACES/2 seconds in normal ifup runs.
# When ifup is called by /etc/init.d/network at boot time, the check
# is done, but /etc/init.d/network waits WAIT_FOR_INTERFACES seconds
# for all interfaces togerther. Set to 0 to disable it.
#
IPV6_DAD_WAIT=""
## Type: string
## Default: ''
#
# Set this variable global variable to the ISO / IEC 3166 alpha2
# country code specifying the wireless regulatory domain to set.
# When not empty, ifup-wireless will be set in the wpa_supplicant
# config or via 'iw reg set' command.
#
# Note: This option requires a wpa driver supporting it, like
# the 'nl80211' driver used by default since openSUSE 11.3.
# When you notice problems with your hardware, please file a
# bug report and set e.g. WIRELESS_WPA_DRIVER='wext' (the old
# default driver) in the ifcfg file.
# See also "/usr/sbin/wpa_supplicant --help" for the list of
# available wpa drivers.
#
WIRELESS_REGULATORY_DOMAIN=''
## Type: string
## Default: ""
#
# Allows to specify a comma separated list of debug facilities used
# by wicked. Negated facility names can be prepended by a "-", e.g.:
# "all,-events,-socket,-objectmodel,xpath,xml,dbus"
#
# When set, wicked debug level is automatically enabled.
# For a complete list of facility names, see: "wicked --debug help".
#
WICKED_DEBUG=""
## Type: list("",error,warning,notice,info,debug,debug1,debug2,debug3)
## Default: ""
#
# Allows to specify wicked debug level. Default level is "notice".
#
WICKED_LOG_LEVEL=""
## Type: yesno
## Default: no
#
# Enable netconfig verbose reporting.
#
NETCONFIG_VERBOSE="no"
## Type: yesno
## Default: no
#
# This variable enables netconfig to always force a replace of modified
# files and automatically enables the -f | --force-replace parameter.
#
# The purpose is to use it as workaround, when some other tool trashes
# the files, e.g. /etc/resolv.conf and you observe messages like this
# in your logs on in "netconfig update" output:
# ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched.
#
# Please do not forget to also report a bug as we have a system policy
# to use netconfig.
#
NETCONFIG_FORCE_REPLACE="no"
## Type: string
## Default: ""
#
# Allows to specify options to use when writting the /etc/resolv.conf,
# for example:
# "debug attempts:1 timeout:10"
# See resolv.conf(5) manual page for details.
#
NETCONFIG_DNS_RESOLVER_OPTIONS=""
## Type: string
## Default: ""
#
# Allows to specify a sortlist to use when writting the /etc/resolv.conf,
# for example:
# 130.155.160.0/255.255.240.0 130.155.0.0"
# See resolv.conf(5) manual page for details.
#
NETCONFIG_DNS_RESOLVER_SORTLIST=""
## Type: integer
## Default: ""
#
# How log to wait for IPv6 autoconfig in ifup when requested with
# the auto6 or +auto6 tag in BOOTPROTO variable.
# When unset, a wicked built-in default defer time (10sec) is used.
#
AUTO6_WAIT_AT_BOOT=""
## Type: list(all,dns,none,"")
## Default: ""
#
# Whether to update system (DNS) settings from IPv6 RA when requested
# with the auto6 or +auto6 tag in BOOTPROTO variable.
# Defaults to update if autoconf sysctl (address autoconf) is enabled.
#
AUTO6_UPDATE=""
## Type: list(auto,yes,no)
## Default: "auto"
#
# Permits to specify/modify a global ifcfg default. Use with care!
#
# This settings breaks rules for many things, which require carrier
# before they can start, e.g. L2 link protocols, link authentication,
# ipv4 duplicate address detection, ipv6 duplicate detection will
# happen "post-mortem" and maybe even cause to disable ipv6 at all.
# See also "man ifcfg" for further informations.
#
LINK_REQUIRED="auto"
我更改了这个文件并重新启动了服务器：
myserver: # cat /etc/sysconfig/clock
TIMEZONE="Europe/Berlin"
DEFAULT_TIMEZONE="Europe/Berlin"
SYSTOHC="yes"
不幸的是，输出date仍在使用旧值（美国/太平洋）。
myserver: # date
Fr 31. Aug 04:34:21 PDT 2018
如何在 SUSE Linux Enterprise Server 12 SP3 上更新本地时间？
SUSE Enterprise Linux Server 11 SP4的发行说明说：
SDK 上的可选编译器已更新至 GCC 5.2。它带来了 C++ 语言支持的改进，包括运行时库和编译器中的完整 C++11 支持以及对大多数 C++14 更改的支持。
听起来很棒！但是当我实际查看 SDK ISO 时，我在任何地方都看不到 GCC 5，只有 GCC 4.8。
# cat media.1/products
/ SUSE-Linux-Enterprise-Software-Development-Kit-11-SP4 11.4.4-1.55
# find /mnt -name '*gcc*'
/mnt/suse/x86_64/cross-spu-gcc-4.3.4_20091019-0.37.24.x86_64.rpm
/mnt/suse/x86_64/cross-spu-gcc-static-4.3.4_20091019-0.37.24.x86_64.rpm
/mnt/suse/x86_64/gcc33-fortran-32bit-3.3.3-11.9.x86_64.rpm
/mnt/suse/x86_64/gcc33-32bit-3.3.3-11.9.x86_64.rpm
/mnt/suse/x86_64/gcc33-3.3.3-11.9.x86_64.rpm
/mnt/suse/x86_64/gcc33-fortran-3.3.3-11.9.x86_64.rpm
/mnt/suse/x86_64/gcc43-fortran-32bit-4.3.4_20091019-0.37.30.x86_64.rpm
/mnt/suse/x86_64/gcc43-gij-4.3.4_20091019-0.37.46.x86_64.rpm
/mnt/suse/x86_64/gcc43-objc-4.3.4_20091019-0.37.30.x86_64.rpm
/mnt/suse/x86_64/gcc43-objc-32bit-4.3.4_20091019-0.37.30.x86_64.rpm
/mnt/suse/x86_64/gcc43-ada-4.3.4_20091019-0.37.30.x86_64.rpm
/mnt/suse/x86_64/gcc43-fortran-4.3.4_20091019-0.37.30.x86_64.rpm
/mnt/suse/x86_64/gcc43-gij-32bit-4.3.4_20091019-0.37.46.x86_64.rpm
/mnt/suse/x86_64/gcc43-java-4.3.4_20091019-0.37.46.x86_64.rpm
/mnt/suse/x86_64/gcc43-obj-c++-4.3.4_20091019-0.37.30.x86_64.rpm
/mnt/suse/x86_64/gcc48-fortran-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc48-32bit-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc48-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc48-c++-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc48-fortran-32bit-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc48-info-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc48-locale-4.8.3+r212056-2.17.x86_64.rpm
/mnt/suse/x86_64/gcc-ada-4.3-62.200.2.x86_64.rpm
/mnt/suse/x86_64/gcc-fortran-4.3-62.200.5.x86_64.rpm
/mnt/suse/x86_64/gcc-fortran-32bit-4.3-62.200.5.x86_64.rpm
/mnt/suse/x86_64/gcc-gij-32bit-4.3-62.200.2.x86_64.rpm
/mnt/suse/x86_64/gcc-gij-4.3-62.200.2.x86_64.rpm
/mnt/suse/x86_64/gcc-java-4.3-62.200.2.x86_64.rpm
/mnt/suse/x86_64/gcc-objc-4.3-62.200.2.x86_64.rpm
/mnt/suse/x86_64/gcc-objc-32bit-4.3-62.200.2.x86_64.rpm
/mnt/suse/x86_64/gcc-obj-c++-4.3-62.200.2.x86_64.rpm
我猜发行说明是错误的，但很乐意以其他方式显示。
SUSE 是否为 SLSE 11 提供比 SLES 11 SP4 SDK 中的 GCC 4.8 更新的编译器？