zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
	"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Check for NIS
Date: Tue, 22 Aug 2000 18:07:41 +0000	[thread overview]
Message-ID: <1000822180741.ZM7800@candle.brasslantern.com> (raw)
In-Reply-To: <001201c00c2e$d1063dd0$21c9ca95@mow.siemens.ru>

On Aug 22,  3:47pm, Andrej Borsenkow wrote:
} Subject: Check for NIS
}
} We check for NIS by testing return value of ypcat. I am not sure it
} is correct way to do it (actually, I am pretty sure, it is the wrong
} way). ypcat may fail if system currently is not configured for NIS;
} or no server temporary is available. It has nothing to do with having
} needed functions and headers that we actually intend to check for.

The reason the test is done this way is that if the functions are present
but the system is not configured, then it becomes very slow for zsh to
attempt YP and then fall back on other methods.

The intent is to make a best guess at whether YP is configured, and skip
it entirely if not, even if the libraries to enable it might be present.
Yes, the test may be wrong if the server is temporarily unavailable, but
this was the best compromise we could come up with at the time.

There should be some discussion of this in the zsh-workers archive from
about three years ago (maybe longer).

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2000-08-22 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-22 11:47 Andrej Borsenkow
2000-08-22 18:07 ` Bart Schaefer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1000822180741.ZM7800@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).