From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: gethostname max len
Date: Sun, 28 Mar 2004 08:48:35 +1000 [thread overview]
Message-ID: <87brmh9a9o.fsf@zip.com.au> (raw)
In-Reply-To: CMM.0.92.0.1080312462.beebe@psi.math.utah.edu
"Nelson H. F. Beebe" <beebe@math.utah.edu> writes:
>
> One correspondent suggested using PATH_MAX.
Not quite, I think the topic drifted. PATH_MAX is of course unrelated
to gethostname.
> (1) There has been great historic variability in the name of the
> parameter that holds the size of the longest possible path; see
> below.
I don't think there's many places depending on path length. getcwd
for instance has a malloc strategy.
The readdir_r I'm proposing will depend on NAME_MAX, but it follows
what the glibc manual says, so it can't be all bad.
The alternative to readdir_r is a mutex to protect the DIR. A single
global mutex might hurt parallelism though, if readdir goes away for a
longish time talking NFS or whatever.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-03-27 22:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 14:47 gethostname max len Nelson H. F. Beebe
2004-03-27 22:48 ` Kevin Ryde [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-21 22:22 Kevin Ryde
2004-03-22 1:05 ` Wolfgang Jaehrling
2004-03-22 1:02 ` Kevin Ryde
2004-03-22 1:34 ` Wolfgang Jaehrling
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87brmh9a9o.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).