search for: deweirdt

On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi <toracat at elrepo.org> wrote: > > On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt <stijn.deweirdt at ugent.be> wrote: >> latest kmod update 20-15.el7_4.6 is broken on our systems, while >> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). >> >> the issue is with modules from mellanox kmod rpms that are symlinked in >> the weak-updates d...

hi all, latest kmod update 20-15.el7_4.6 is broken on our systems, while previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). the issue is with modules from mellanox kmod rpms that are symlinked in the weak-updates dir. the config files in /etc/depmod.d look ok (and do work with previous version): dist.conf has weak-updates after built-in, and mellanox kmod rpms ship a

On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt <stijn.deweirdt at ugent.be> wrote: > hi all, > > latest kmod update 20-15.el7_4.6 is broken on our systems, while > previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). > > the issue is with modules from mellanox kmod rpms that are symlinked in > the weak-updates dir...

...still no clue how to report issues to centos team to doublecheck packaging mishaps... stijn On 02/06/2018 12:49 AM, Akemi Yagi wrote: > On Tue, Jan 2, 2018 at 10:10 AM, Akemi Yagi <toracat at elrepo.org> wrote: >> >> On Thu, Dec 7, 2017 at 6:23 AM, Stijn De Weirdt <stijn.deweirdt at ugent.be> wrote: > >>> latest kmod update 20-15.el7_4.6 is broken on our systems, while >>> previous 20-15.el7_4.4 was working fine (and downgrading fixes the issue). >>> >>> the issue is with modules from mellanox kmod rpms that are symlinked in >&g...

Hi folks, For complicated reasons, I'd like to have a service (lightdm) start after sshd starts. (This is on CentOS 7.) I've tried adding "sshd.service" to the lists of "Active=" and "Require=" items in /etc/systemd/system/lightdm.service (which started as a copy of /usr/lib/systemd/system/lightdm.service), but these changes don't seem to have

hi all, i'm stuck debugging a problem that appeared after this update made it to our systems: http://lists.centos.org/pipermail/centos-announce/2015-January/020856.html GDBM_File fails simple operation (which works with 1.8.0-36 of gdbm) could someone with same perl and gdbm confirm the issue via simple script below? (would help me narrow down if this is something specific on our

hi brian, isn't the attribute named Requires (with an s)? stijn On 02/20/2015 07:50 PM, Bryan Wright wrote: > Hi folks, > > For complicated reasons, I'd like to have a service (lightdm) start > after sshd starts. (This is on CentOS 7.) I've tried adding "sshd.service" > to the lists of "Active=" and "Require=" items in >

hi johnny, apologies, yes this is centos7 on x86_64. i had to set PKGCONFIG_DIR, but that looked like the only thing. i'll give mock a try and see what comes out. thanks a lot stijn On 02/15/2017 10:44 AM, Johnny Hughes wrote: > On 02/15/2017 03:41 AM, Johnny Hughes wrote: >> On 02/15/2017 02:39 AM, Stijn De Weirdt wrote: >>> hi all, >>> >>> i'm

hi johnny, >> anyone any hints how to debug this or some clues what could be going >> wrong here. > > Do you have an exclude in /etc/yum.conf for ibutils-libs? how embarassing. there was indeed an exclude on ibutils-libs. (this must be some leftover from using mlnx ofed. we are switching from c73+mlnx ofed 3.4 to c74 stock ib (there's no mlnxofed3.4 for c74, and our old

hi all, in case someone else runs into it, it is the opfed-scripts rpm that has a postinstall and postuninstall script that changes the yum.conf (bad, mellanox, bad) for a pure/regular uninstall it works fine, but to swap ibutils from mlnxofed to ib stack from os, yum obviously doesn't know that the exclude will be removed. i've seen worse in vendor-provided rpms, but i guess it caught

hi all, we have hosts that we want to pxeboot first, always. with uefi, anaconda/kickstart always set the freshly installed disk as first bootdevice and there seems to be no way to disable this behaviour. the rhel7 docs describe a "leavebootorder" option (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/installation_guide/sect-kickstart-syntax) but it

hi all, i'm trying to understand an issue i'm having with a yum repo (it's a mirror of the c74 repo). there's an rpm in the repo (ibutils-libs in this case); but the client using this repo says it cannot find this rpm (i did yum info ibutils-libs --disablerepo=* --enablerepo=c74 to exclude all other repos). other rpms are ok to use, so nothing structural going wrong (i think)

hi all, can someone help explaining what we are seeing? it makes no sense to us. this is a host running centos 7.4 with 3.10.0-693.17.1 kernel, and it has 192GB of ram > [] free -b > total used free shared buff/cache available > Mem: 201402642432 14413479936 75642777600 48586752 111346384896 185689632768 > Swap: 21474832384 31961088

Hi, I'm using rsync to backup my data from my Linux machine (SUSE10.1) and Windows (XP) I've mounted a windows share on my linux and I'm trying now to copy files to the windows with rsync. The windows share is a NTFS filesystem It's all working except I have a error on large files. This is the command that I'm trying: rsync -a --no-o --delete

hi all, i'm trying to rebuild the current sssd-client.i686 rpm that is part of the x86_64 repo, but i fail to do so. rebuilding the sssd.src.rpm on x86_64 does not produce this rpm. i can rebuild sssd.src.rpm with --target=i686, but that sssd-client rpm has conflicts and a whole bunch of i686 deps that the rpm from the centos repo doesn't have. tips/help welcome stijn

hi all, i have a general question (a bit surprised ti's not on the centos faq): we found a bug in a package in a centos install, and we are wondering what the best approach is to get TUV to fix it (and release an update), so it gets fixed in centos rebuild and thus on our nodes. or at the very least to get it on their todo list ;) bugs.centos.org seems an obvious candidate to get them

Hello everyone. I''ve been toying around with puppet and something happened that seems strange to me. In site.pp I have the following: > node default { > > # This is where you can declare classes for all nodes. > > # Example: > > # class { ''my_class'': } > > # class { ''lamp'': } > > package