similar to: mlocate/updatedb and btrfs subvolume mounts

I set this computer up with Centos 8 a few days ago. "systemctl status mlocate-updatedb.timer" says "Active (waiting)". But the mlocate database hasn't been updated since the last time I ran updatedb manually. # ls -l /var/lib/mlocate/* -rw-r-----. 1 root slocate 22944208 Feb 29 10:30 /var/lib/mlocate/mlocate.db What have I missed? -- MELVILLE THEATRE ~ Real D 3D

On Mon, 2 Mar 2020 09:16:16 -0600 Frank Cox wrote: > I set this computer up with Centos 8 a few days ago. > > "systemctl status mlocate-updatedb.timer" says "Active (waiting)". > > But the mlocate database hasn't been updated since the last time I ran > updatedb manually. Just to follow this up, the mlocate database update started working automatically

Yeah, Dominique, your wiki was one of the many docs I read through before/during/after starting down this primrose path... thanks for writing it. I'm an Arch user, and I couldn't find anything to indicate qemu, as its compiled for Arch, will look in /etc/default/qemu-kvm. And now that I've got the right page size, the instances are starting... The reason I want to use the page element

Hi list For some reason mlocate is taking a long time when I run the updatedb command. Have a look! [root at beta:~] #time updatedb real 19m48.729s user 0m0.400s sys 0m2.728s It's not a big volume by any means [root at beta:~] #df -h Filesystem Size Used Avail Use% Mounted on /dev/xvda1 75G 9.1G 63G 13% / So I'm wondering what could be causing

I've been having intermittent network issues on my Host - they go away when I stop and disable libvirtd and then reboot. They do not go away if I just stop libvirtd and don't reboot. I'm at a loss as to where to start with my troubleshooting, and being a relative n00b to libvirt, I'd love any pointers. Regards, Richard

Hello All, I'm trying to enable hugepages, I've turned off THP (Transparent Huge Pages), and enabled hugepages in memoryBacking, and set my 2MB hugepages count via sysctl. I'm getting "libvirtd[5788]: Failed to autostart VM 'atlas': internal error: Unable to find any usable hugetlbfs mount for 16777216 KiB" where atlas is one of my guests and 16777216 KiB is the

CentOS Errata and Bugfix Advisory 2012:1355 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1355.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 7354cb6599a1e82fcd99ffa03561ed84f5b31e05250357cf610ed38af37c804e mlocate-0.22.2-4.el6.i686.rpm x86_64:

CentOS Errata and Bugfix Advisory 2015:0676 Upstream details at : https://rhn.redhat.com/errata/RHBA-2015-0676.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9d76f451da0b0d8f11a0f7fcccabe7b84338026ddc5f60353c0fb89910c253f0 mlocate-0.22.2-6.el6.i686.rpm x86_64:

----- KSR[T] Website : http://www.dec.net/ksrt E-mail: ksrt@dec.net ----- KSR[T] Advisory #003 Date: Aug 05, 1997 ID #: lin-cron-003 Operating System(s): Redhat linux 4.1, SuSE Linux 5.0, Slackware 3.3 Affected Program:

It turns out that if you specify filesystem type `auto' in /etc/fstab, updatedb (the thing which updates your `locate' database) ceases to work. Here's the contents of my /etc/updatedb.conf: PRUNEFS="devpts NFS nfs afs proc smbfs autofs auto iso9660" PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net" export PRUNEFS export PRUNEPATHS deleting the `auto' entry

[Mod: Headers modified -- alex] If this is already known, my apologies. It seemed very strange that this worked, so I thought it would be mentionable. On many linux systems(Redhat imparticularly) updatedb is run nightly around 1:00. When it sorts the files that find gets, it creats a few files in /tmp called sort0<pid>000{1,2,etc}. Each is around 512k. The first file is created and filled,

We have seen at a number of deployments, users experiencing slowness of GlusterFS over a period of time (as the volume usage grows). Some times it happens once in a day. This is due to updatedb cron job script that wakes up once in a day to index all the files it can find. It is configured by default to ignore network file systems such as NFS and lustre. Please add fuse.glusterfs to the list.

Hello everyone, I am trying to adjust the systemd-logind classification of the SSH session opened by Ansible client. By default the SSH session created by Ansible client is Class=user and Type=tty in systemd-logind. pam_systemd.so allows users to change this default via the environment variables XDG_SESSION_CLASS and XDG_SESSION_TYPE. When I set these variables on the client and make sure they

*facepalm* Now that I'm re-reading the documentation it's obvious that <page/> and @nodeset are for the guest, "This tells the hypervisor that the guest should have its memory allocated using hugepages instead of the normal native page size." Pretty clear there. Thank you SO much for the guidance, I'll return to my tweaking. I'll report back here with my results.

Hi, What is the best way to deal with I/O load when running several VMs on a physical machine with local or remote storage? What I'm primarily worried about is the case when several VMs cause disk I/O at the same time. One example would be the "updatedb" cronjob of the mlocate package. If you have say 5 VMs running on a physical System with a local software raid-1 as storage and

On Mon, 16 Dec 2024, Michal Sekletar wrote: > Hello everyone, > > I am trying to adjust the systemd-logind classification of the SSH > session opened by Ansible client. By default the SSH session created > by Ansible client is Class=user and Type=tty in systemd-logind. > pam_systemd.so allows users to change this default via the environment > variables XDG_SESSION_CLASS and

On Tue, Dec 17, 2024 at 5:40?AM Damien Miller <djm at mindrot.org> wrote: > User-specified environment variables are not propogated to the > environment where sshd invokes PAM modules because the SSH protocol > sends them at the time a session is opened, well after authentication > has completed. At best, they could be made available to the PAM > session modules but

On ???, 16 ??? 2024, Michal Sekletar wrote: > Hello everyone, > > I am trying to adjust the systemd-logind classification of the SSH > session opened by Ansible client. By default the SSH session created > by Ansible client is Class=user and Type=tty in systemd-logind. > pam_systemd.so allows users to change this default via the environment > variables XDG_SESSION_CLASS and

I was just wondering if there are special tricks people do that compile A LOT on centos? Do RAM disks help or something else I dont about that minimizes your compile time? I presently have and AMD x2 4800+ with 2GIG ram. Just curious if I can reduce any more time out of my compiles. Jerry

hi. I'm trying to install a program using winetricks, but I'm using a separate wine install and WINEPREFIX, I run any command as such - WINEARCH="win32" WINE='/home/de/media_writeit!/FOSS/additional packages/Wine prefixes/Works with wine 1.3.32/wine-1.3.32' WINEPREFIX='/home/de/media_writeit!/temp(others)/walkthrough' ./winetricks And it returns -