bind_wait uses ypwatch without a full path

[jwm]

Binary package hint: nis

The bind_wait function in /etc/init.d/nis calls ypwhich to see if the NIS server is up, but as it runs the command without a full path, it will always fail in contexts where a PATH has not been set.

This appears to be true of all versions of the init script installed up to Hardy.

Prepending /usr/bin to the three instances of ypwhich fixes the problem, but you may wish to set a variable like ${NET}.

[Chuck Short (zulcss)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

[Chuck Short (zulcss)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[jwm (jwm-angrymonkey)]

Everything you need to know to determine if this bug report still applies to the Karmic NIS package is *in the bug report*.

I suggest someone try reading it and following the instructions.

[Steve Langasek (vorlon)]

Running an init script from a context in which /usr/bin is not on the path is invalid. Therefore closing this report, as it would be incorrect to embed a qualified path in the init script to address this.