Ubuntu
rpcbind package

  1. Bug #1007293
  2. Comment #16

Comment 16 for bug 1007293

Revision history for this message
vagk (vagk-p) wrote :

>This shows that ypbind is being started as soon as portmap starts. But the start condition for ypbind is:
>
>start on (started portmap ON_BOOT=
> or (started portmap ON_BOOT=y
> and ((filesystem and static-network-up) or failsafe-boot)))

>So it appears that portmap is being started with ON_BOOT= instead of with ON_BOOT=y, confusing ypbind into believing that as >soon as portmap starts, ypbind can also be started.

>I believe this is due to a bug in either the portmap-wait or the statd job, one of which needs to set ON_BOOT=y.

I tried changing /etc/init/ypbind.conf reversing the conditions just to test
   start on (started portmap ON_BOOT=y
        or (started portmap ON_BOOT=
            and ((filesystem and static-network-up) or failsafe-boot)))

The boot process delayed in 2 points (between 9 to 19 sec and after 30 sec)

ypbind started successfully!

Does this verify your assumptions of where the problem is?