All of lore.kernel.org
 help / color / mirror / Atom feed
* strange regression in ldap support between 5.3 and 5.4
@ 2009-05-18 19:50 Guillaume Rousse
  2009-05-19  2:48 ` Ian Kent
  0 siblings, 1 reply; 4+ messages in thread
From: Guillaume Rousse @ 2009-05-18 19:50 UTC (permalink / raw)
  To: autofs

Hello list.

I have a user reporting a strange regression after updating from linux 
mandriva 2009.0 (shipping autofs 5.0.3 + all patches until 
fix-couple-of-memory-leaks.patch) to mandriva 2009.1 (shipping autofs 
5.4 + all patches until clear-rpc-client-on-lookup-fail.patch): 
apparently, keys defined in indirect maps are mounted directly on the 
mount point, instead of a subdir:

https://qa.mandriva.com/show_bug.cgi?id=50631

The debug output is apparently not consistent with mount output:
mounted /home/lsc/luizd
vs
sol.lsc.ufsc.br:/export/lsc/home/luizd on /home/lsc type nfs

Curiously, file based maps works OK. But, the only ldap-related changes 
I see in the applied patches set (5.0.3 with all patches is basically 
5.0.4) is a memory leak fix, and a build-time detection fix.

Does someones see something else ?

-- 
BOFH excuse #323:

Your processor has processed too many instructions.  Turn it off 
immediately, do not type any commands!!

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: strange regression in ldap support between 5.3 and 5.4
  2009-05-18 19:50 strange regression in ldap support between 5.3 and 5.4 Guillaume Rousse
@ 2009-05-19  2:48 ` Ian Kent
  2009-05-19  4:49   ` Ian Kent
  2009-05-19 16:25   ` Guillaume Rousse
  0 siblings, 2 replies; 4+ messages in thread
From: Ian Kent @ 2009-05-19  2:48 UTC (permalink / raw)
  To: Guillaume Rousse; +Cc: autofs

Guillaume Rousse wrote:
> Hello list.
> 
> I have a user reporting a strange regression after updating from linux 
> mandriva 2009.0 (shipping autofs 5.0.3 + all patches until 
> fix-couple-of-memory-leaks.patch) to mandriva 2009.1 (shipping autofs 
> 5.4 + all patches until clear-rpc-client-on-lookup-fail.patch): 
> apparently, keys defined in indirect maps are mounted directly on the 
> mount point, instead of a subdir:
> 
> https://qa.mandriva.com/show_bug.cgi?id=50631
> 
> The debug output is apparently not consistent with mount output:
> mounted /home/lsc/luizd
> vs
> sol.lsc.ufsc.br:/export/lsc/home/luizd on /home/lsc type nfs
> 
> Curiously, file based maps works OK. But, the only ldap-related changes 
> I see in the applied patches set (5.0.3 with all patches is basically 
> 5.0.4) is a memory leak fix, and a build-time detection fix.
> 
> Does someones see something else ?

Looks like the trailing "/" on the autofs mount point might be causing
some confusion:

dn: cn=/home/lsc/,nisMapName=auto.master,ou=autofs,ou=nss,dc=lsc,dc=ufsc,dc=
 br
cn: /home/lsc/
nisMapName: /home/lsc/
objectClass: nisObject
objectClass: top
nisMapEntry: ldap:lua.lsc.ufsc.br:nisMapName=auto.home,ou=autofs,ou=nss,dc=l
 sc,dc=ufsc,dc=br


I'd be interested to know if this is the case.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: strange regression in ldap support between 5.3 and 5.4
  2009-05-19  2:48 ` Ian Kent
@ 2009-05-19  4:49   ` Ian Kent
  2009-05-19 16:25   ` Guillaume Rousse
  1 sibling, 0 replies; 4+ messages in thread
From: Ian Kent @ 2009-05-19  4:49 UTC (permalink / raw)
  To: Guillaume Rousse; +Cc: autofs

Ian Kent wrote:
> Guillaume Rousse wrote:
>> Hello list.
>>
>> I have a user reporting a strange regression after updating from linux 
>> mandriva 2009.0 (shipping autofs 5.0.3 + all patches until 
>> fix-couple-of-memory-leaks.patch) to mandriva 2009.1 (shipping autofs 
>> 5.4 + all patches until clear-rpc-client-on-lookup-fail.patch): 
>> apparently, keys defined in indirect maps are mounted directly on the 
>> mount point, instead of a subdir:
>>
>> https://qa.mandriva.com/show_bug.cgi?id=50631
>>
>> The debug output is apparently not consistent with mount output:
>> mounted /home/lsc/luizd
>> vs
>> sol.lsc.ufsc.br:/export/lsc/home/luizd on /home/lsc type nfs
>>
>> Curiously, file based maps works OK. But, the only ldap-related changes 
>> I see in the applied patches set (5.0.3 with all patches is basically 
>> 5.0.4) is a memory leak fix, and a build-time detection fix.
>>
>> Does someones see something else ?
> 
> Looks like the trailing "/" on the autofs mount point might be causing
> some confusion:
> 
> dn: cn=/home/lsc/,nisMapName=auto.master,ou=autofs,ou=nss,dc=lsc,dc=ufsc,dc=
>  br
> cn: /home/lsc/
> nisMapName: /home/lsc/

And shouldn't nisMapName be auto.master?

> objectClass: nisObject
> objectClass: top
> nisMapEntry: ldap:lua.lsc.ufsc.br:nisMapName=auto.home,ou=autofs,ou=nss,dc=l
>  sc,dc=ufsc,dc=br
> 
> 
> I'd be interested to know if this is the case.
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: strange regression in ldap support between 5.3 and 5.4
  2009-05-19  2:48 ` Ian Kent
  2009-05-19  4:49   ` Ian Kent
@ 2009-05-19 16:25   ` Guillaume Rousse
  1 sibling, 0 replies; 4+ messages in thread
From: Guillaume Rousse @ 2009-05-19 16:25 UTC (permalink / raw)
  Cc: autofs

Ian Kent a écrit :
> I'd be interested to know if this is the case.
You were right :)

-- 
BOFH excuse #361:

Communist revolutionaries taking over the server room and demanding all 
the computers in the building or they shoot the sysadmin. Poor misguided 
fools.

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2009-05-19 16:25 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-05-18 19:50 strange regression in ldap support between 5.3 and 5.4 Guillaume Rousse
2009-05-19  2:48 ` Ian Kent
2009-05-19  4:49   ` Ian Kent
2009-05-19 16:25   ` Guillaume Rousse

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.