amd with nis-maps?

[Dirk Luetjens <dirk@plus.lfm.rwth-aachen.de>]

Hello,

I have a small problem using amd with nis maps. The problem rises when
referring to the directory where the nis map is mounted. Let me explain
it step by step:

- I created I master amd map with the following contest
>/test amd.nis 
>/test2 /root/amd.home 
where amd.nis is the NIS map:
># polka
>helmut  -sublink:=${key};rfs:=/local \
>        host==polka;type:=link;fs:=/local 
and /root/amd.home is a local map with:
># plus
>dirk    -sublink:=${key};rfs:=/local \
>        host==plus;type:=link;fs:=/local \
>        host!=plus;type:=nfs;rhost:=plus
>plus    -sublink:=${key};rfs:=/local \
>        host==plus;type:=link;fs:=/local \
>        host!=plus;type:=nfs;rhost:=plus

- I started the amd with the options amd ... -D all ... 
  The Debug-Messages shows me that amd started ok with both map types.
>...
>Sep 23 13:27:35 plus amd.debug[11070]: Map for /root/amd.home coming from maptype file
>Sep 23 13:27:35 plus amd.debug[11070]: calling map reload on /root/amd.home
>...
>Sep 23 13:27:35 plus amd.debug[11070]: NIS master for amd.nis@lfm has order 843475795
>Sep 23 13:27:35 plus amd.debug[11070]: Map for amd.nis coming from maptype nis
>Sep 23 13:27:35 plus amd.debug[11070]: amd.nis mounted fstype toplvl on /test
 
- When I list the content of /test2 with "ls /test2", I get
>dirk plus
  That's ok.

  But, when I do "ls /test", I get although
>dirk plus
  That is not ok.

- Ok, restart the amd again, and do first "ls /test"	
  The amd dies, and the shell stops produceing output until ctrl-c.

Looking at the Debug-Messages gives:

plus:~# ls /test2
dirk plus
>...
>Sep 23 13:33:01 plus amd.debug[11091]: default search
>...
plus:~# ls /test
dirk plus
>...
>Sep 23 13:33:03 plus amd.debug[11091]: default search
>...

The same happens when first referring to the NIS map. The last output
from amd is
>...
>Sep 23 13:33:01 plus amd.debug[11091]: default search
Afterwards the amd dies.


I tried to install the NIS map as a local file to, and everything is ok.
So it looks, that the problem is hidden in the NIS map. It seems that
there is an uninitialized pointer, wich causes the amd to die, when
first reference the NIS map, and when referenced another Map before to
use the same pointer again.

Is there any solution for this problem?

I forgot:

I'm using the debian-1.1/stable tree with amd_upl102-3.deb.

Thank you very much.

I will report this as a bug to. Yet, I don't know how. It's my first bug
:-). 

Dirk