similar to: 40 second delay on automounts with 2.6.18-53.1.21.el5 kernel

i had previously been having issues with automount being slow with this new kernel and i tracked it down to dns delays which were being caused by ipsec not working. i have spent a few hours poking around and ipsec seems quite broken with this new kernel. esp packets go in and out just fine, but when i look at ip xfrm stats on the machine with the new kernel, i see that for input packets,

i (and others) have missed messages on centos-devel as well. did other people not see the 4.7 announcement message? i'm wondering if the centos list server is having some kind of issue.

See Red Hat Bugzilla bug #846852 for details. https://bugzilla.redhat.com/show_bug.cgi?id=846852 FYI: We discovered that after updating to EL 6.3 on our x86_64 server, autofs 5.0.5-54 broke our nightly backups that rely on automounting an NFS share hosted on another EL 6 machine on our local network. The machine hosting NFS server was configured to allow only TCP connections to the port

while in firefox if i use arrow keys in text fields, it acts very oddly. starting at the beginning of the line it works fine for a few characters and then jumps to the end of the line. backarrow jumps backwards from the end of line to within a few chars of the beginning. anyone else seeing this?

Hi Is there any way to re-export an nfs mounted directory? I am having three servers runnning on centos4.5 and i am trying to implement nfs share in an below manner [bcoz there is no alternative way for me to setup nfs share] HOST A--->>>EXPORTS /prod/data ------->>>HOST B HOST B ---->>MOUNTED ------>>> /prod/data-----UNDER---/PROD1 [working fine] HOST B

i see one available in the repos, but i don't recall seeing any announcement about it. from googling, it does seem to be real, but still a bit disconcerting to not have an announcement about it.

sorry i figured this out after deleting the other parts of the thread. just run vino-preferences as the user who runs the main x display. it will have various options to enable and as soon as you do that you can get to hostname:0 via vnc. works quite well.

i've downloaded the new 2.6.9-34 kernel src rpm and keep getting signature issues or md5 issues if i tell rpm to ignore signatures. it seems that maybe the master copy is corrupted?

there doesn't seem to be a src.rpm for the newest kernel up on mirror.centos.org. i need to apply a local patch. is it the same as the upstream version? also, the centosplus unsupported version is either missing the -doc package or people need to know to do some manual intervention to get the regular version to replace the old unsupported version.

Been a week, any eta? :) Thanks! -- Matthew Kent \ SA \ bravenet.com

redhat did apply the opendesktop patch to build the iso8859-1 fonts, but then they forgot to rebuild the fonts-xorg package to pick them up. they have done some magic with how that happens such that you have to build the full xorg-x11 with a special %define set, and then go rpm2cpio stuff and tar that and blah blah blah. i am trying to work through this and i have whined at redhat again. and

Just popped back on the list because I was curious about this. I've read the information about virtualization and other new features. I'm just wondering (as someone who installed CentOS 2 years ago and basically hasn't thought much about it my OS other than using it since then) if any piece of it except for virtualization got updated significantly enough to consider an upgrade. My

On Mon, 10 Apr 2023 at 07:07, Peter Stuge <peter at stuge.se> wrote: > > Brian Candler wrote: > > > What's odd is that the length is *always* 1231976033 (which is > > > 0x496E7661 or "Inva" in ASCII). One thing that can cause this is if the libc writes to stderr (ie fd 2) on some classes of error. This is something libc should probably not do, since

the rsync in centos 4 (a recompile of rhel4) is version 2.6.3. and under certain circumstances it will segfault when run in daemon mode. i have tracked it down to the nss code in libc. so this could be a general libc bug, but it is possible that rsync is doing things that don't help matters any. the problem manifests when you have chroot mode on (which seems to be the default), have

I am experimenting with Matt McCutchen's excellent continusync script, and I'm having an issue. (My copy of continusync has been modified from the original http://mattmccutchen.net/utils/continusync by adding this @ line 227: <$fromInwt>; as suggested by Matt.) The problem is easily reproduced: # mkdir ~/foo # continusync ~/foo root@remotehost:~/foo & # vi

Hi! Thanks to some of you I got autofs set up on my C7 netbook for mounting local cifs filesytems. Now I want to do something on my C7 desktop machine, that seems to me to be a little different, and I"m not sure how to do it. I have an external RAID1 box that attaches via USB. It is/will be nearly always /dev/sdc, but being USB I can't guarantee that it will always be found there.

After yum upgrade, the new CentOS5 kernel [ kernel-2.6.18-92.1.1.el5.i686 ] crashes each time early in boot process on Compaq ProLiant 3000 with dual Pentium3 CPU (600 MHz, CPU0: Intel Pentium III (Katmai) stepping 03, CPU1 the same). I get kernel panic at powernowk8_init+0x05e/0x1c3. The previous kernel [ kernel-2.6.18-53.1.21.el5.i686 ] seems to work fine. I am wondering if anyone has met

On Thu, Jun 08, 2017 at 04:02:05PM -0700, Kenneth Porter wrote: > Automounting is now done through systemd. In my use, we continue to use autofs for automounts of CIFS volumes, because as best I can tell, systemd doesn't support using the request-key infrastructure to use a user's kerberos ticket to set up the automount. -- Jonathan Billings <billings at negate.org>

On Thu, 2023-09-21 at 20:08 -0400, Kevin Korb via rsync wrote: > I have heard in the past that rsyncing an empty dir over a tree to > delete the tree is faster than an rm -rf but I can't say I have ever > benchmarked it to get any actual numbers. This **may** indeed be a myth (for a long time now) re-cited again and again and - could no longer be valid today - could apply only

On Fri, Jun 9, 2017 at 6:18 AM, Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > On Fri, Jun 09, 2017 at 08:25:31AM -0400, Jonathan Billings wrote: >> On Thu, Jun 08, 2017 at 04:02:05PM -0700, Kenneth Porter wrote: >> > Automounting is now done through systemd. >> >> In my use, we continue to use autofs for automounts of CIFS volumes, >> because as