Description of problem:

As the following shows locking works correctly.
And lckpwdf correctly (?) creates a lock file
"/etc/.pwd.lock".
However that file doesn't appear to be used for locking,
just created as a side-effect!  And ulckpwdf doesn't
remove the file!

Version-Release number of selected component (if applicable):

Probably all, but:
glibc-common-2.6-4
glibc-devel-2.6-4
glibc-headers-2.6-4
glibc-2.6-4
shadow-utils-4.0.18.1-15.fc7 

"uname -a" shows (in part):
Linux localhost 2.6.23.1-21.fc7

How reproducible:

Always.

Steps to Reproduce:

cat >lckpwdf-test.c <<\EOF
#include <stdio.h>
#include <shadow.h>
int main (void) {
   int status = lckpwdf();
   printf("(status=%d) hit enter to quit: ", status);
   getchar();
   status = ulckpwdf();
   return status;
}
EOF

# make lckpwdf-test
# ls -l /etc/.pwd.lock  # IT ISN'T THERE TO START WITH:
ls: cannot access /etc/.pwd.lock: No such file or directory

# ./lckpwdf-test
(i=0) hit enter to quit:

# echo $?
0

# ls -l /etc/.pwd.lock  # THE FILE SHOULD HAVE BEEN REMOVED, BUT:
-rw------- 1 root root 0 2007-12-31 10:06 /etc/.pwd.lock

# ./lckpwdf-test &  SHOULDN'T WORK IF THE LOCK FILE IS THERE, BUT:
[1] 12414
(i=0) hit enter to quit:
[1]+  Stopped                 ./lckpwdf-test

# ls -l /etc/.pwd.lock
-rw------- 1 root root 0 2007-12-31 10:48 /etc/.pwd.lock

# ./lckpwdf-test  # THIS SHOWS LOCKING WORKS REGARDLESS OF THE LOCK FILE:
(i=-1) hit enter to quit:

# echo $?  # CORRECTLY FAILS WHEN ANOTHER PROCESS HAS THE LOCK:
255

# fg
./lckpwdf-test


# echo $?
0

# ls -l /etc/.pwd.lock  # SHOULD HAVB BEEN REMOVED, BUT:
-rw------- 1 root root 0 2007-12-31 10:48 /etc/.pwd.lock