On a SLES 12 virtual machine the command rpm -qa does not return anything to stdout.
~> rpm -qa
~>
The command finishes after 1 or 2 seconds, so it clearly generates some data. Only when the output is redirected to a file or through a pipe it becomes visible:
~> rpm -qa > out.txt # works fine
~> rpm -qa | grep lib
libgcc ...
...
The problem is not with the rpm DB, the DB files in /var/lib/rpm/ are existing and seem healthy, a rebuild as suggested here does not solve the problem.
I have a Postgres v10 Server to which only local connections will be established. In the documentation I find two methods to configure such an authentication process in pg_hba.conf: local and host with 127.0.0.1:
# Allow any user on the local system to connect to any database with
# any database user name using Unix-domain sockets (the default for local
# connections).
#
# TYPE DATABASE USER ADDRESS METHOD
local all all trust
# The same using local loopback TCP/IP connections.
#
# TYPE DATABASE USER ADDRESS METHOD
host all all 127.0.0.1/32 trust
Are there any best practices or security concerns over which type (Unix Domain Socket vs TCP/IP Socket) I should choose, as they seem to be both applicable to my usecase? Of course I will select another auth-method other than "trust".
I never used dracut so far. I understood dracut filesystems (Wiki) as temporary systems that help mounting system specific kernel modules during the boot process. But after successful boot of my SLES 12 Server VM I still have a dracut file system under /var/tmp/dracut.2jqPCx.
Do I still need it? Where do I find information about how to get rid of this extra file system? Or, if it is essential, were do I find information about the reasoning for keeping it after the boot process?