From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
there appears to be a dependancy issue starting /etc/init.d/nfslock on
boot:

- rpc.statd is not started on boot, but the /var/lock/subsys/nfslock
file is created.  this suggests a bug in /etc/init.d/functions::daemon

- rpc.statd can be started (with restart) after a normal boot

- prc.statd will be started normally if the run level is moved to, for
example, 99 and the machine is rebooted


all the above suggest a dependancy issue but i cannot say more.  as it
is the failure to start rpc.statd means any application requiring nfs
safe locks (fcntl) will fail with errno ENOLCK.

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


How reproducible:
Always

Steps to Reproduce:
1. reboot
2. change to a nfs mounted directory
3. run any program which uses fctnl based locks, eg

  #include <stdlib.h>
  #include <stdio.h>
  #include <sys/types.h>
  #include <sys/stat.h>
  #include <fcntl.h>
  #include <unistd.h>
  int
  main (argc, argv)
       int argc;
       char **argv;
  {
    char path[42];
    int fd;
    struct flock lock;
    sprintf (&path[0], "nfslockXXXXXX");
    if ((fd = mkstemp (&path[0])) == -1)
      {
        fprintf (stderr, "mkstemp failed with %d\n", fd);
        return EXIT_FAILURE;
      }
    lock.l_type = F_RDLCK;
    lock.l_whence = SEEK_SET;
    lock.l_start = lock.l_len = 0L;
    return(fcntl (fd, F_SETLKW, &lock));
  }

(compile with and run 'a.out || echo 'nfslocking failed!')

Actual Results:  failure

Expected Results:  success

Additional info:

i looked into the script only sofar as to determine that that call to
'daemon' results in a $RETVAL of 0 and so the lock file is touched,
yet no rpc.statd is running.  i assume that rpc.statd was not started
(do not know why) AND that daemon returns ?$==0 for this condition
(which it should not)