search for: altsystem

> > But if I start the automount unit and ls the mount point, the shell hangs > and eventually, a long time later (I haven't timed it, maybe an hour), I > eventually get a prompt again. Control-C won't interrupt it. I can still > ssh in and get another session so it's just the process that's accessing > the mount point that hangs. > I don't have a

> > Why? 7.5.1804 has been out since May of this year. You're going to > end up downloading a ton of updates the first time. > For a specialized software, we have to wait for the developers to certify each new OS. They are still recommending 7.3. One reason in particular is that 7.5 has a fix for Meltdown and Spectre, which known to reduce performance. This machine will be

Kenneth Porter wrote: > --On Friday, October 19, 2018 2:33 PM -0700 Elliott Balsley > <elliott at altsystems.com> wrote: > >> I don't have a solution, but I wanted to point out this same hang >> happened to me recently with a Myricom 10Gb card. Apparently Myricom >> drivers do not support CentOS 7 smb connections, although HTTP traffic >> works fine. I solved it by swi...

--On Friday, October 19, 2018 2:33 PM -0700 Elliott Balsley <elliott at altsystems.com> wrote: > I don't have a solution, but I wanted to point out this same hang happened > to me recently with a Myricom 10Gb card. Apparently Myricom drivers do > not support CentOS 7 smb connections, although HTTP traffic works fine. I > solved it by switching to a differen...

On a 8 Core system only dom0 can set cap > 100 and vcpus > 1. On a domU ''xm sched-credit -d <domU> -c 200'' says "Error: cap is out of range". Vcpu cannot be set higher than 1 - regardless of boot/config/command line. Low performance is equivalent to the cap setting. See ''xm list --long'': (domain (domid 0) (uuid

> Hmmm... It works for me on both CentOS 7 (Firefox 60.2.1) and Fedora 28 > (Firefox 62.0.3). > > As per the linked documentation - What happens if you SHIFT-CLICK on the > scroll bar? On my systems I find that SHIFT-CLICK on the scroll bar > produces > the "warp speed" behavior, exactly as expected. > > >

In CentOS 7.3 the gnome-system-monitor shows one big graph for CPU usage. Now in CentOS 7.5 I see a red box for each core. On a machine with lots of CPU cores, this is taking up too much screen real estate, so is there some way to go back to the old behavior?

Is there some way to see what version will be installed by an installation disc? I made a USB installer and I forgot whether it's CentOS 7.3 or 7.5. Short of running the whole installer and seeing what happens, I can't see any way to get this info from within Anaconda.

Hello. I am using Samba 4.8.3 on CentOS 7 and I am seeing a strange error in the log. I have usershare max shares = 1 and I have exactly one share defined. Every time I list shared with *smbclient -L* I see this line in the log: [2019/09/11 17:41:30.413727, 0] ../source3/param/loadparm.c:3755(load_usershare_shares) load_usershare_shares: too many total entries (2) in directory

> > I agree that issue with the scroll bar jumping all over is really > annoying! > It is actually a feature of Gnome and GTK. It can be changed by editing a > file: > > ~/.config/gtk-3.0/settings.ini > > [Settings] > gtk-primary-button-warps-slider=0 > > I also find this behavior annoying. I tried adding this settings file (it didn't exist) and logging

Hi all, I'm having trouble doing a fresh install of CentOS 7.3. I'm using the DVD installer ISO, burned to a USB flash drive. The system is a Supermicro 7048 with four Nvidia Titan Xp GPUs, and I have the monitor connected to the first GPU. In the BIOS, VGA priority is set to Offboard, so I am seeing POST messages (good). The CentOS installer begins and shows a few messages on my

> From a end state perspective, it does not matter . . yum update after > the install (of either) ends at exactly the same place. I will not be running any updates, because I need to keep a specific old version for software compatibility. I don't know which ISO the USB stick was made from. > > Also, a 'uname -a' from the command prompt will tell you .. This would be