tags 98407 = wontfix
severity 98407 minor
retitle 98407 nvi init script runs before NIS is up
thankyou

Hi,

there's not much I can do about this. The present situation is:

* Networking is available at S:40.
* Nvi is installed at S:70.
* Nis is called in the multi-user runlevels only, [2-5]:19.

Nis won't get moved into S (that would defeat the single- / multi-
user runlevel concept), and Nvi can't be moved out of S because,
as Steve has pointed out, we want to send mail for recoverable
files _once_.

But usually this scenario doesn't pose a problem:
* Either you are a client on the NIS network; then you most probably
  don't do the mail delivery yourself, but have a central smarthost
  that handles the mail traffic for the whole network, so you don't
  need to have nis running when sending mail (as the smarthost will
  check if the local part is a valid user name).
* Or you are the mail server of the NIS network - but in this case
  it's rather unlikely that there are tons of users editing files
  on it.

All I can offer is to note the fact in nvi's README and tag the bug
accordingly.


Regards,

Jan

Attachment: signature.asc
Description: Digital signature

Reply via email to