similar to: Missing autofs update for C5?

CentOS Errata and Security Advisory 2007:1176 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-1176.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 003005a1904e2d7b86c7e78752ae91b6 autofs-5.0.1-0.rc2.55.el5.2.i386.rpm Source: dbed45d348006960ac0976c68e01fa46 autofs-5.0.1-0.rc2.55.el5.2.src.rpm

CentOS Errata and Security Advisory 2007:1176 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-1176.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 2bc04b0f86bc0b0a9a31bf5d8bd2d0b0 autofs-5.0.1-0.rc2.55.el5.2.x86_64.rpm Source: dbed45d348006960ac0976c68e01fa46

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Security Advisory 2007:1128 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-1128.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 49553c47a0b61fec2e731bbe7e73043e autofs-5.0.1-0.rc2.55.el5.1.x86_64.rpm Source: c28e875dc47f9d20acfac9ff51fe31be

CentOS Errata and Security Advisory 2007:1128 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2007-1128.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: a0b788e2cb59158b4d173db59cf3e030 autofs-5.0.1-0.rc2.55.el5.1.i386.rpm Source: c28e875dc47f9d20acfac9ff51fe31be autofs-5.0.1-0.rc2.55.el5.1.src.rpm

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

On top of my previously (just now) difficulties with yum, now I find that the 53.1.6 kernel is not installing properly. When I run "yum update" to install it, the install hangs here: Dependencies Resolved ============================================================================= Package Arch Version Repository Size

List, When running the downloaded Base ISO - Installtion programm it aborts due to packages which seem to be damaged: el5.3bin... el4.5... el5.1 el4.6 dom0fs.... tools-iso... various rpms etc..... any idea? How to overcome the situation for a real beginner ? Thanks -- Liebe Grüße / Best Regards Thomas Wehr _______________________________________________ Xen-users mailing list

I've posted this question to the Gnome users list, but so far no luck, so I thought I'd mention this here. A little while ago, I noticed that I was no longer able to log out from my GDM. I'm running the default GDM (2.16) that comes with CentOS, and this problem started up right about the same time that I updated to the 53.1.4 kernel (from the 8.1.15 version). As I've posted

"yum update" output: ............................... --> Running transaction check --> Processing Dependency: libgoffice-1.so.2 for package: gnumeric ---> Package goffice.i386 0:0.6.6-1.el5.rf set to be updated --> Finished Dependency Resolution 1:gnumeric-1.6.3-15.el5.2.i386 from installed has depsolving problems --> Missing Dependency: libgoffice-1.so.2 is needed by

it's strange since this kernel don't have kvm support, qemu or qemu-kvm or kvm package is not added. even though it was said that 5.4 will support kvm?:-( Tom "spot" Callaway wrote: > New Packages in RHEL 5.4 Beta: > ******************************** > blktrace-1.0.0-6.el5.src.rpm > celt051-0.5.1.3-0.el5.src.rpm > etherboot-5.4.4-10.el5.src.rpm >

On Wed, Aug 23, 2017 at 01:59:23PM -0700, Gordon Messmer wrote: > On 08/23/2017 01:06 PM, Fred Smith wrote: > >so, the two lines saying: Key "syno-fredex" or key "syno-public" > >appear whenever I try to access one of those two filesystems. I AM NOT > >USING AUTOFS TO MANAGE THEM. > > > You're using autofs to manage /mnt, so any time that

On Wed, Aug 23, 2017 at 12:03:12PM -0700, Gordon Messmer wrote: > On 08/21/2017 07:23 PM, Fred Smith wrote: > >so, in my case, the USB drive contains an xfs filesystem. would I > >do something like this: > > > >in /etc/auto.master: > >backup /etc/auto.backup > > > >and in /etc/auto.backup > >backup -fstype=xfs,defaults,noauto,users

Hi, I'm using Autofs and LDAP for mounting my home directories via nfs. In general, everything seems to work fine. However, I have one small problem. If I reboot my server using autofs while my LDAP server is down, I get the following error message in my logs: automount[3358]: bind_ldap_anonymous: lookup(ldap): Unable to bind to the LDAP server: (default), error Can't contact LDAP

Hi, I am still trying to figure out the best settings for Samba and Kerberos with autofs. My setup so far works good, users can log in on their computers using AD credentials, and they can access network shares with AD credentials as well. This works perfect. Also I notice that some Kerberos ticket is created upon user login, which allows the users to access a Samba share without entering the

Was trying to use autofs on ubuntu and mounting a samba shared failed. Then, i came across a note that 'unless you need to authenticate to cifs' -- wish I could find the exact quote now. The point is autofs fails to mount a windows server share. I can mount the share using mount.cifs but it fails with autofs. So I just thought I would check to see if anyone has pointers on using autofs on

We have about 800 CentOS 5.2 servers and our university. We use NFS being served from over 10 NetApp frames. We use autofs for to mount up our partitions. There have been times where we can't cd into the directory. It says the directory does not exist. On some servers it works but on others it does not. Typically we restart amd and autofs to resolve this issue. But sometimes it does not even

CentOS Errata and Bugfix Advisory 2012:0506 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-0506.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: a6d3c7f8b2ee1c0c7494a07a58a7dadcbb4d68b0c03e9d3419472031e3a0bcdc autofs-5.0.1-0.rc2.164.el5_8.i386.rpm x86_64:

CentOS Errata and Bugfix Advisory 2014:1240 Upstream details at : https://rhn.redhat.com/errata/RHBA-2014-1240.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: f02b5b33d83fb0d0f7ab28401d9408bf076d1110043fc000086d5d2fd8086dd2 autofs-5.0.1-0.rc2.184.el5.i386.rpm x86_64:

Hi, Does setting the autofs timeout=0 create a permanent mount? What I'm trying to do is get the best of both world; 1) Have a persistent mount so that users can use autocompletion. 2) utilize the benefits of autofs so that when an NFS resource becomes unavailable, the system doesn't hang. I've tried a timeout of 0 but it doesn't seem to work.