Olaf Mueller wrote: > Olaf Mueller wrote: > > >> Olaf Mueller wrote: >> >>> since kernel 2.6.18-164.el5 no user could login any more from nfs >>> client into his home directory >>> >> Now reported on CentOS Bug Tracker #0003840. >> > Here are some more information and a workaround. > > This is a know major flaw as reported on > https://bugzilla.redhat.com/show_bug.cgi?id=522163. > Since the previous kernel 2.6.18-128.7.1.el5 is not up to date with > security fixes and the current kernel 2.6.18-164.el5 isn't usable as a > nfs server, I have installed kernel 2.6.18-165.el5.jtltest.87, you will > find it in the bug report, as a workaround. This is not optimal cause > I think this is a testing kernel for RHEL 5.5 (not 5.4!), but it seems > to me the best choice as a kernel under CentOS 5.3 at the moment if you > are running an nfs server. And only the nfs server needs this kernel to > work, the clients can stay with the current kernel 2.6.18-164.el5. > > > regards > Olaf > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > Am I missing something here? We use and love CentOS for its stability and the fact(?) that the upstream provider does extensive QA(?) Now we have a major regression in the 5.4 kernel and the proposal in the bug fix is wait until 5.5 for the patch? or do it yourself - something I do not look forward to doing. Is someone dropping the ball or am I over-reacting? Rob -------------- next part -------------- A non-text attachment was scrubbed... Name: rkampen.vcf Type: text/x-vcard Size: 121 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20090917/c027864a/attachment-0004.vcf>