search for: linux7

We are seeing a problem that occurs ~5% of the time when rebooting CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just after the D-Bus service starts - from 'journalctl -x' : ... Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System Message Bus. -- Subject: Unit dbus.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dbus.service has finished starting up. -- -- The start-up result is done. Jan 21 1...

...; now is to simply > reboot the server again in such a case, AKA the systemd way :-) > >> CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just >> after the D-Bus service starts - from 'journalctl -x' : >> >> ... >> Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System >> Message Bus. >> -- Subject: Unit dbus.service has finished start-up >> -- Defined-By: systemd >> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >> -- >> -- Unit dbus.service has finished sta...

...on it. My "solution" now is to simply reboot the server again in such a case, AKA the systemd way :-) > CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just > after the D-Bus service starts - from 'journalctl -x' : > > ... > Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System > Message Bus. > -- Subject: Unit dbus.service has finished start-up > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit dbus.service has finished starting up. > -- > -...

...reboot the server again in such a case, AKA the systemd way :-) >> >>> CentOS 7.7 where systemd gets a 'Connection timed out' to D-Bus just >>> after the D-Bus service starts - from 'journalctl -x' : >>> >>> ... >>> Jan 21 16:09:59 linux7-7.mpc.local systemd[1]: Started D-Bus System >>> Message Bus. >>> -- Subject: Unit dbus.service has finished start-up >>> -- Defined-By: systemd >>> -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel >>> -- >>> -- Unit dbus....

Hi, I'm trying to build Wine as a 32 bit program on my x86_64 machine, running Fedora Core 2. I downloaded Wine-20040914.tar.gz specified that I wanted to use the 32-bit compilers with: CC=/usr/bin/i386-redhat-linux7-gcc CXX=/usr/bin/i386-redhat-linux7-g++ CPP_FLAGS=-m32 CXXFLAGS=-m32 ./configure I then did make depend and make, and everything appears to be being built with the correct compilers until: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ./ddraw.spec convert.o dclipper/main.o dd...

...ommand used to configure: ./configure --prefix=/usr/local/openssh --sysconfdir=/etc/openssh --with-pam --with-ssl-dir=/usr/local/openssl I am not subscribed to this list. So ple. send me email. -subu ----------------------------------------------- root at linux7 openssh-3.8p1]# rpm -qa | grep pam pam-0.75-14 pam_krb5-1.46-1

I''m running SLES10 SP1 and have been using file:/ for my file-backed domUs. The domUs sit on a shared OCFS2 SAN-backed filesystem and are run on my three or four XEN servers. I''m having issues with the loopback devices not being released when the domUs shutdown or migrate, so I decided to switch over to tap:aio for my file-backed domUs. This isn''t working, either.