I need to install npm in my suse distribution, so naturally I followed https://software.opensuse.org/download.html?project=devel%3Alanguages%3Anodejs&package=nodejs and https://nodejs.org/en/download/package-manager/#opensuse-and-sle but I got the same error and I didn't find out a way to fix it. **Details** $ rpm -qf /etc/SuSE-release /etc/issue sles-release-11.4-1.109 $ sudo zypper ar http://download.opensuse.org/repositories/devel:/languages:/nodejs/SLE_11_SP4/ Node.js $ sudo zypper refresh $ sudo zypper clean $ sudo zypper update $ sudo zypper install nodejs > Loading repository data... Reading installed packages... Resolving > package dependencies... > > Problem: nothing provides openssl1 needed by nodejs-6.9.1-130.1.x86_64 > Solution 1: do not install nodejs-6.9.1-130.1.x86_64 Solution 2: > break nodejs-6.9.1-130.1.x86_64 by ignoring some of its dependencies > > Choose from above solutions by number or cancel [1/2/c] (c):

I'm encountering an issue where I'm unable to execute multiple alias commands at the same time in my shell environment. For example, when I try to run two alias commands together, only one seems to execute, or I get an error. I've tried defining the aliases separately and then combining them in a single command using && and ;, but it still doesn't work as expected. Here's a simplified version of what I'm trying: alias1 alias2

I'm encountering an issue where I'm unable to execute multiple alias commands at the same time in my shell environment. For example, when I try to run two alias commands together, only one seems to execute, or I get an error. The below example shows that what I am exactly trying If I want to copy file.txt from one system another system, we scp command. So, i was trying scp -i auth_key file.txt userid@target_hostname:/target/path/ alias1= 'scp -i auth_key' alias2= 'userid@target_hostname:/target/path/' I was trying to execute the below command alias1 file.txt $alias2

I have updated my Suse Tumbleweed system, and consequently a new kernel version has been installed. To reclaim space used by an _ancient_ kernel, I decided to use the zypper purge-kernels command, and here it is what happened:

$ df / ; sudo zypper purge-kernels ; df /
Filesystem              1K-blocks     Used Available Use% Mounted on
/dev/mapper/system-root  36700160 27053812   8861788  76% /
[sudo] password for root: 
Reading installed packages...

Preparing to purge obsolete kernels...
Configuration: latest,latest-1,running
Running kernel release: 6.15.4-1-default
Running kernel arch: x86_64

Resolving package dependencies...

The following 3 packages are going to be REMOVED:
  bbswitch-kmp-default-0.8_k6.15.3_2-14.42 kernel-default-6.15.3-2.1
  ovpn-dco-kmp-default-0.2.20241216~git0.a08b2fd_k6.15.3_2-3.17

3 packages to remove.

Package install size change:
              |         0 B    required by packages that will be installed
  -258.5 MiB  |  -  258.5 MiB  released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): 
(1/3) Removing: bbswitch-kmp-default-0.8_k6.15.3_2-14.42.x86_64 ..............[done]
(2/3) Removing: ovpn-dco-kmp-default-0.2.20241216~git0.a08b2fd_k6.15.3_2-3.17.[done]
(3/3) Removing: kernel-default-6.15.3-2.1.x86_64 .............................[done]
Running post-transaction scripts .............................................[done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
 
Since the last system boot core libraries or services have been updated.
Reboot is suggested to ensure that your system benefits from these updates.
Filesystem              1K-blocks     Used Available Use% Mounted on
/dev/mapper/system-root  36700160 27463068   8455604  77% /
$

After releasing 258.5 MiB of disk space, I end up with an increased occupation of 397 KiB. I suspect that Suse saves the data somewhere and for good measure adds some book-keeping stuff, but I'd like a confirmation of these suspects and also 1. an explanation of this behavior (if you need more detail, as usual ask in comments), 2. how can I prevent such behavior. --- _Addendum_ I tried rebooting, to see if some disk space was held away from running processes, but I found that it was not my case.

I am having trouble updating a SLES 12.5 server. Zypper is not working supposedly due to another zypper process already running:

# zypper lu
System management is locked by the application with pid 25074 (zypper).
Close this application before trying again.

If I try again, the PID changes:

# zypper lu
System management is locked by the application with pid 27117(zypper).
Close this application before trying again.

If I try to kill 27117, it doesn't work as it is not there anymore:

# kill 27117
bash: kill: (27117) - No such process

The PID is stored in

# cat /var/run/zypp.pid
31776

and here too, if I repeat the command, I get a different PID:

# cat /var/run/zypp.pid
525

This is what zypper.log looks like when I issue a zypper lu command:

2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(main):97 ===== Hi, me zypper 1.13.64
2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(main):98 ===== 'zypper' 'lu' =====
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(_autodetectSystemArchitecture):73 Uname architecture is 'x86_64'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(_autodetectTextLocale):209 Default text locale is 'en'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(Impl):343 libzypp: 16.22.8
2023-10-10 22:10:52  myhostname(27119) [zypp] IniParser.cc(parse):84 Start parsing /etc/zypp/zypp.conf[g___]
2023-10-10 22:10:52  myhostname(27119) [zypp] IniParser.cc(parse):138 Done parsing /etc/zypp/zypp.conf[_eF_]
2023-10-10 22:10:52  myhostname(27119) [Progress++] ProgressData.cc(report):88 {#1|/etc/zypp/zypp.conf}END
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(Impl):621 ZConfig singleton created.
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 libzypp: 16.22.8
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 libsolv: 0.6.39
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 zypp.conf: '/etc/zypp/zypp.conf'
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 TextLocale: 'en' (en)
2023-10-10 22:10:52  myhostname(27119) [zconfig] ZConfig.cc(ZConfig):821 SystemArchitecture: 'x86_64' (x86_64)
2023-10-10 22:10:52  myhostname(27119) [zypp] PathInfo.cc(assert_dir):354 mkdir /var/tmp/zypp.hVcxMA/zypper 00755
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(Zypper):552 Zypper instance created.
2023-10-10 22:10:52  myhostname(27119) [zypper] media.h(MediaCallbacks):182 Set media callbacks..
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):891 START
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 START MEASURE(ReadConfig)
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):21 Going to read zypper config using Augeas...
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):103 Done reading conf files:
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):108 user conf read: no
2023-10-10 22:10:52  myhostname(27119) [zypper] Augeas.cc(Augeas):109 global conf read: yes
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 ELAPSED(ReadConfig) 0 (u 0.01 s 0.00 c 0.00)
2023-10-10 22:10:52  myhostname(27119) [Measure] Measure.cc(log):178 MEASURE(ReadConfig) 0 (u 0.01 s 0.00 c 0.00) [0 (u 0.00 s 0.00 c 0.00)]
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1019 Verbosity 1
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1020 Output type 1
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1280 repos.d dir = /etc/zypp/repos.d
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1281 cache dir = /var/cache/zypp
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1282 raw cache dir = /var/cache/zypp/raw
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1283 solv cache dir = /var/cache/zypp/solv
2023-10-10 22:10:52  myhostname(27119) [zypper++] Zypper.cc(processGlobalOptions):1284 package cache dir = /var/cache/zypp/packages
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):1296 Repositories enabled
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processGlobalOptions):1414 DONE
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):1606 START
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):3536 Done parsing options.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(processCommandOptions):3555 Done
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(_openLockFile):168 Open lockfile /var/run/zypp.pid
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(readLockFile):223 read: Lockfile /var/run/zypp.pid has pid 27117 (our pid: 27119)
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(isProcessRunning):195 Checking /proc/27117{d 0555 0/0}
2023-10-10 22:10:52  myhostname(27119) [zypp++] ZYppFactory.cc(isProcessRunning):209 Is running: zypper
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(zyppLocked):270 27117 is running and has a ZYpp lock. Sorry.
2023-10-10 22:10:52  myhostname(27119) [zypp] ZYppFactory.cc(_closeLockFile):186 Close lockfile /var/run/zypp.pid
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 ZYppFactory.cc(getZYpp):404 THROW:    System management is locked by the application with pid 27117 (zypper).
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Close this application before trying again.
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(assertZYppPtrGod):267 CAUGHT:   System management is locked by the application with pid 27117 (zypper).
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Close this application before trying again.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(assertZYppPtrGod):303 A ZYpp transaction is already in progress.
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.h(setExitCode):250 setExitCode 7
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(assertZYppPtrGod):307 THROW:    ZYpp locked
2023-10-10 22:10:52  myhostname(27119) [zypp] Exception.cc(log):166 Zypper.cc(safeDoCommand):1582 CAUGHT:   ZYpp locked
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(safeDoCommand):1583 Caught exit request: exitCode 7
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(cleanup):5575 START
2023-10-10 22:10:52  myhostname(27119) [zypper] main.cc(~Bye):82 ===== Exiting main() =====
2023-10-10 22:10:52  myhostname(27119) [zypper] Zypper.cc(~Zypper):559 Zypper instance destroyed. Bye!
2023-10-10 22:10:52  myhostname(27119) [zypp] PathInfo.cc(recursive_rmdir):435 recursive_rmdir /var/tmp/zypp.hVcxMA
2023-10-10 22:10:52  myhostname(27119) [zypp++] TmpPath.cc(~Impl):78 TmpPath cleaned up /var/tmp/zypp.hVcxMA{d 0700 0/0}

Any idea of what could be going on here? I have solved this in the past by rebooting, but I want to find a better, not so drastic solution. **UPDATE**: I never found the solution, but I found a rude workaround. Since the PID keeps changing that means that after a process closes and before the new one is spawn, there is a time gap where I can run zypper lu. So I just try again and again until I hit that gap and it works just fine.

I am using a SUSE Linux Enterprise Desktop in a virtual environment with a VMware SVGA II Adapter. I need to rotate my screens using xrandr, but every time I try to do so, I get the following error:

xrandr: output Virtual1 cannot use rotation "left" reflection "none"

Here is some relevant information about my setup: - Graphics Adapter: VMware SVGA II Adapter (driver: vmwgfx) - Display Server: X11 (X.Org version 1.21.1.4) - Driver: vmwgfx (OpenGL v: 4.5 Mesa 22.3.5) - VM Environment: VMware VDI When I run inxi -G, it gives me:

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0
  Display: x11 server: X.Org v: 1.21.1.4 driver: gpu: vmwgfx note: X driver n/a - try sudo/root
  API: OpenGL v: 4.5 Mesa 22.3.5 renderer: llvmpipe (LLVM 15.0.7 256 bits)

What I’ve tried: - Using xrandr to rotate the screen (xrandr --output Virtual1 --rotate left) - Checked for any VMware or SUSE settings that might enable screen rotation None of these have worked. Is there any way to enable screen rotation using xrandr or another tool while using the VMware SVGA II Adapter in a VDI environment? Any suggestions or workarounds would be greatly appreciated!

I have created a shared folder **/data01/share** on one Suse Gnu/Linux and also made entry for host(client) machine in **/etc/exports** **/data01/share  10.241.200.53(rw,sync,no_root_squash,no_subtree_check)** . But i am getting this after **exportfs -a** exportfs: No options for /data01/share  10.241.200.53(rw,sync,no_root_squash,no_subtree_check) : suggest (sync) to avoid warning exportfs: /etc/exports : Neither 'subtree_check' or 'no_subtree_check' specified for export ":/data01/share  10.241.200.53(rw,sync,no_root_squash,no_subtree_check)". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x exportfs: Failed to stat /data01/share  10.241.200.53(rw,sync,no_root_squash,no_subtree_check): No such file or directory **cat /etc/os-release** NAME="SLES" VERSION="12-SP3" VERSION_ID="12.3" PRETTY_NAME="SUSE Linux Enterprise Server 12 SP3" ID="sles" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:12:sp3" **systemctl status nfs-server.service** nfs-server.service - NFS server and services Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled) Drop-In: /usr/lib/systemd/system/nfs-server.service.d └─nfsserver.conf /run/systemd/generator/nfs-server.service.d └─order-with-mounts.conf Active: active (exited) since Wed 2019-07-24 02:32:03 EDT; 2h 34min ago Main PID: 2562 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 512) CGroup: /system.slice/nfs-server.service Jul 24 02:32:03 OPT001CORE0002 systemd: Starting NFS server and services... Jul 24 02:32:03 OPT001CORE0002 systemd: Started NFS server and services. **cat /etc/exports** # See the exports(5) manpage for a description of the syntax of this file. # This file contains a list of all directories that are to be exported to # other computers via NFS (Network File System). # This file used by rpc.nfsd and rpc.mountd. See their manpages for details # on how make changes in this file effective. /data01/share  10.241.200.53(rw,sync,no_root_squash,no_subtree_check) **ls -la /data01/share** total 0 drwxrwxrwx 4 acmuser acmgrp 36 Jul 24 04:18 . drwxr-xr-x 6 acmuser acmgrp 65 Jul 24 04:16 .. drwxrwxrwx 3 acmuser acmgrp 18 Jul 24 04:18 support drwxrwxrwx 5 acmuser acmgrp 45 Jul 24 04:17 upgrade

I have gone through this link https://stackoverflow.com/questions/10940296/installing-python-2-7-on-sles-11 and followed the instructions as suggested. I have created the bash file and executed that bash file somewhere between I got the error. So that I have executed the command step by step it was installed successfully. But while execute python in terminal it still showing python 2.6.9 version. Please let me know any other alternative solution to install python 2.7.12 in SUSE Machine.

I am in the middle of an activity and have never worked with SLES10 SP4 In SLES11 zypper update glibc* updates all glibc packages .. but this is not working in SLES10 SP4 .. can someone tell me how to update a single package in SLES10 SP4

My client is trying to install SAP application on Suse 15 SP3, usually this error does not occur, but whenever they are executing install for SAP they are unable to bypass dependencies for python-openssl. I have to tried to install the package 'python-openssh' but unable to get it as it not showing up in results for command 'zypper search-packages python-openssl'. I have also tried to find for rpm package for this but that too ended in failure.

I found several similar questions but AFICT they don't apply to my situation. Some [e.g. this one for tmux](https://unix.stackexchange.com/questions/171503/tmux-session-killed-when-disconnecting-from-ssh) and elsewhere on Ubuntu suggest it is due to using ssh.socket, but my install is not even using that, it is still on ssh.service. I found some suggestions for disabling the auto logout on timeout, but I don't want to disable it, I want screen to be running when I log back in. If I exit from ssh (with ~.). I saw somewhere it is related to when the service starts. Could it be preset: disabled setting of OpenSSH Daemon? $> systemctl status ssh* ● sshd.service - OpenSSH Daemon Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled; preset: disabled) Active: active (running) since Thu 2024-10-17 22:58:56 UTC; 4 months 3 days ago Process: 2107 ExecStartPre=/usr/sbin/sshd-gen-keys-start (code=exited, status=0/SUCCESS) Process: 2110 ExecStartPre=/usr/sbin/sshd -t $SSHD_OPTS (code=exited, status=0/SUCCESS) Main PID: 2112 (sshd) Tasks: 1 CPU: 14.713s CGroup: /system.slice/sshd.service └─2112 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

How to set the system clock sync with RTC (Hardware Clock / BIOS). I am writing a script that uses a system clock in order to start the system with alarm. For this the sole requirement is to have a proper RTC clock. On my test system (SLES 10 SP4), I use NTP Server to manage the system clock. But the RTC clock is always ahead. So for example : currently the system clock shows 14:00 26.05.2016 and the RTC shows 16:00 Hrs. I read the man pages of hwclock and it shows that following command

hwclock --systohc --localtime

would sync the RTC clock to system clock. Which it did. But after a reboot/shutdown, when the system comes up again, the RTC is again messed up. So there is something more which controls the RTC when the system is rebooted. Could someone point me in the right direction. Thanks in advance.

I am currently installing SuSE Linux 15. I wish to secure this system against Disk failure hence opted to configure software RAID 1 on disk1 (sda) and disk2 (sdb). Basically during installation configured the disks partitions in RAID 1 and then created following partitions. /boot/efi md0 (sda2+sdb2) /boot md1 (sda3+sdb3) /swap md2 (sda4+sdb4) / md3 (sda5+sdb5) I then tested this system, by removing sdb system, and the system could boot without problem. But when I removed the disk sda(primary) disk, the system could not go part Grub. After analysing, I have realised the Grub is configured in such a way that it points to software raid parition md1 but it must have both the disks present, ie working software raid, in order to be able to boot the system using that device md1. I am not okay with this if this is really true. The basic idea of having software raid for /boot device is that in case of hardware failure, the system should use the other working disk and boot. Isn't it the software raid 1 meant for? I am really confused now. If you require any more system details please ask. But how do i secure the system (boot) against hardware failure. The disks do eventually fail. So there must be some solution. It just that I do not know it yet. Regards. Here is the output of the commands you asked for, localhost:~ # lsblk -f | grep -v loop | sed -E 's/\w{8}-\w{4}-\w{4}-\w{4}-\w{12}/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX/' NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda ├─sda1 ├─sda2 linux_raid_member 1.0 any:0 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ├─sda3 linux_raid_member 1.0 any:1 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX ├─sda4 linux_raid_member 1.0 any:2 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX │ └─md2 swap 1 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX [SWAP] └─sda5 linux_raid_member 1.0 any:3 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX sdb ├─sdb1 ├─sdb2 linux_raid_member 1.0 any:0 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX │ └─md0 vfat FAT32 ADB7-4EE5 1021.9M 0% /boot/efi ├─sdb3 linux_raid_member 1.0 any:1 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX │ └─md1 ext4 1.0 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX 853.8M 7% /boot ├─sdb4 linux_raid_member 1.0 any:2 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX │ └─md2 swap 1 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX [SWAP] └─sdb5 linux_raid_member 1.0 any:3 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX └─md3 ext4 1.0 XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX 4.4G 54% / sr0 iso9660 Joliet Extension SLE-15-SP6-Full-x86_6493.51.001 2024-06-13-19-56-33-00 localhost:~ # fdisk -l Disk /dev/sda: 15 GiB, 16106127360 bytes, 31457280 sectors Disk model: VBOX HARDDISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 0E77630A-CBC9-4C1F-9321-D7886DAC09BC Device Start End Sectors Size Type /dev/sda1 2048 104447 102400 50M BIOS boot /dev/sda2 104448 2201599 2097152 1G Linux RAID /dev/sda3 2201600 4298751 2097152 1G Linux RAID /dev/sda4 4298752 8493055 4194304 2G Linux RAID /dev/sda5 8493056 31457246 22964191 11G Linux RAID Disk /dev/sdb: 15 GiB, 16106127360 bytes, 31457280 sectors Disk model: VBOX HARDDISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 07F46E03-A25D-4305-BCFD-E79ADEA113C1 Device Start End Sectors Size Type /dev/sdb1 2048 104447 102400 50M BIOS boot /dev/sdb2 104448 2201599 2097152 1G Linux RAID /dev/sdb3 2201600 4298751 2097152 1G Linux RAID /dev/sdb4 4298752 8493055 4194304 2G Linux RAID /dev/sdb5 8493056 31457246 22964191 11G Linux RAID Disk /dev/md1: 1023.94 MiB, 1073676288 bytes, 2097024 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md3: 10.95 GiB, 11757551616 bytes, 22963968 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/md0: 1023.94 MiB, 1073676288 bytes, 2097024 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x00000000 Disk /dev/md2: 2 GiB, 2147418112 bytes, 4194176 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Respective Partitions: /dev/sda1 --> BIOS BOOT Partition /dev/sda2 --> BIOS BOOT Partition /dev/md0 (sda2+sdb2) : /boot/efi /dev/md1 (sda3+sdb3): /boot /dev/md2 (sda4+sdb4): /swap /dev/md3 (sda5+sdb5): /

I have two Suse 15.6 servers, both have the same directories and files; the first example running on a GCP VM and the other on an VMWare VM. Not sure which ENV var I'm missing, since both have declare -x LANG="en_US.UTF-8" and declare -x LS_OPTIONS="-A -N --color=tty -T 0" (not sure if that modifies the output of find in any way) Both servers are running find (GNU findutils) 4.8.0 I need to redirect the output to a file so I can compare them, but for some reason one of them shows the dot files first whilst the other starts by the jre folder.

# find . -type f | less
./.install4j/user/commons-codec.jar
./.install4j/user/commons-httpclient.jar
./.install4j/user/commons-io.jar
./.install4j/user/dom4j.jar
./.install4j/user/flatlaf.jar
./.install4j/user/inception.jar
./.install4j/user/modzdetector.jar
./.install4j/user/slf4j-api.jar
./.install4j/user/slf4j-jdk14.jar
./.install4j/MessagesDefault
./.install4j/files.log
./.install4j/i4j_extf_0_4r1oza.utf8
./.install4j/i4j_extf_1_4r1oza.utf8
./.install4j/i4j_extf_2_4r1oza_1pb4rjn.png
./.install4j/i4j_extf_3_4r1oza_1wyvt5o.png
./.install4j/i4j_extf_4_4r1oza_10elu9m.png
./.install4j/i4j_extf_5_4r1oza_18gg8kx.png
./.install4j/i4j_extf_5_4r1oza_18gg8kx@2x.png
./.install4j/i4j_extf_5_4r1oza_18gg8kx@2x_dark.png
./.install4j/i4j_extf_5_4r1oza_18gg8kx_dark.png
./.install4j/i4j_extf_6_4r1oza_deir7z.png
./.install4j/i4jempty.ttf
./.install4j/i4jparams.conf
./.install4j/i4jruntime.jar
./.install4j/inst_jre.cfg
./.install4j/install.prop
./.install4j/installation.id
./.install4j/installation.log
./.install4j/launcher0.jar
./.install4j/launcher2bfa42ba.jar
./.install4j/libi4jinst.dylib
./.install4j/libi4jinst2.dylib
./.install4j/pref_jre.cfg
./.install4j/response.varfile

find . -type f | less
./jre/bin/rmiregistry
./jre/bin/keytool
./jre/bin/jrunscript
./jre/bin/jfr
./jre/bin/java
./jre/conf/sound.properties
./jre/conf/sdp/sdp.conf.template
./jre/conf/security/policy/unlimited/default_local.policy
./jre/conf/security/policy/unlimited/default_US_export.policy
./jre/conf/security/policy/README.txt
./jre/conf/security/policy/limited/default_local.policy
./jre/conf/security/policy/limited/default_US_export.policy
./jre/conf/security/policy/limited/exempt_local.policy
./jre/conf/security/java.security
./jre/conf/security/java.policy
./jre/conf/net.properties
./jre/conf/logging.properties
./jre/conf/management/jmxremote.password.template
./jre/conf/management/management.properties
./jre/conf/management/jmxremote.access
./jre/legal/java.xml.crypto/santuario.md
./jre/legal/jdk.dynalink/dynalink.md
./jre/legal/java.base/aes.md
./jre/legal/java.base/public_suffix.md
./jre/legal/java.base/ASSEMBLY_EXCEPTION
./jre/legal/java.base/LICENSE
./jre/legal/java.base/icu.md
./jre/legal/java.base/unicode.md
./jre/legal/java.base/c-libutl.md
./jre/legal/java.base/asm.md
./jre/legal/java.base/cldr.md
./jre/legal/java.base/ADDITIONAL_LICENSE_INFO
lines 1-32

sed -i '/tmp\s/ s/subvol/subvol=/@tmp,nodev,noexec,nosuid' /etc/fstab it throws back a termination error... I've tried altering the text using single quotes and double quotes.

**Description:** Have

open suse leap ~15

!!! Can't open

.kde.discover.desktop

file which located in

/home/etc/Documents/Apps/

in folder by created me. **Problems:** 1) May be I removed something and now any

(AnyApp.desktop)

is could not opened in my linux system. This is my 1'st problem today. 2) Snapshots is not working also. **I Try:** 1) And when I was try opening any

.desktop

file by (double click) it just was opened with libreoffice application

(calc)

but it's impossible. 2) In Settings/Applcations/No any workable associated application. (except for the calc).

I want to change an entry in /etc/group - specifically, to add some user to some group. But something - I don't know what or who - has created an /etc/group.lock file. fuser /etc/group.lock gives nothing, but that doesn't tell me much. How can I tell who's the "culprit"? And whether I can safely delete the lock file and be able to change /etc/group again? Note: I'm using SLES 15 on an x86_64 machine.

While installing and running a processd using zypper am getting below error message, the processd is installed, unable to run as expected, Please help, error trying to compare the processd system key: system-key missing on disk Started process Daemon daemon.go:502: gracefully waiting for running hooks daemon.go:504: done waiting for running hooks daemon stop requested to wait for socket activation processd.service: Deactivated successfully.

I have a local repo that has some rpms in it. The repo xmls etc are up to date. When I find an rpm I don't have, I want to be able to download it, not install it obviously, and put that rpm into the repo dir. I see I can use zypper install --download-only but this seems to only work when I haven't got the package installed on my box, else it says 'already' installed. It also doesn't allow me to state the version/edition/rev of the package I want. This is no good to me. How can I get a rpm from my active repositories and store it to a specified location? I don't mind installing a new tool if zypper aint the way to go.

When running service apache start I see in the log file this entry: [mpm_event:notice] [pid 1906:tid XXX] AH00489: Apache/2.4.23 (Unix) OpenSSL/1.0.2g PHP/7.0.9 configured -- resuming normal operations [core:notice] [pid 1906:tid XXX] AH00094: Command line: '/usr/sbin/httpd' [mpm_event:notice] [pid 1906:tid XXX] AH00492: caught SIGWINCH, shutting down gracefully and the service apache does not start? I can find in internet what SIGWINCH means [Window size change] but it does not really help me in this case. The file /etc/systemd/system/apache.service: [Unit] Description=The Apache Webserver [FaF Compiled] After=network.target nss-lookup.target time-sync.target Before=getty@tty1.service plymouth-quit.service xdm.service [Service] Type=notify PrivateTmp=true ExecStart=/usr/sbin/httpd -k start ExecReload=/usr/sbin/httpd -k graceful ExecStop=/usr/sbin/httpd -k graceful-stop KillMode=mixed [Install] WantedBy=multi-user.target Alias=httpd.service apache.service Running on SLES 12 SP1. I have compiled Apache on my own. Starting it with apachectl -k start works perfectly and I can access and run the PHP code. **My question:** What am I doing wrong that the apache service does not start. I have enabled it with systemctl enable apache. This was the output: ln -s '/usr/lib/systemd/system/apache2.service' '/etc/systemd/system/httpd.service' ln -s '/usr/lib/systemd/system/apache2.service' '/etc/systemd/system/apache.service' ln -s '/usr/lib/systemd/system/apache2.service' '/etc/systemd/system/multi-user.target.wants/apache2.service'