diff options
| author | Jarkko Hietaniemi <jhi@iki.fi> | 2002-09-27 04:08:56 +0300 |
|---|---|---|
| committer | hv <hv@crypt.org> | 2002-10-02 15:04:57 +0000 |
| commit | af685957336d0a37645ff959496386c489e0b52a (patch) | |
| tree | 0bf174a4e022dbc1a9ff2cb2ba7ebbd5d8ae436b /pod/perlthrtut.pod | |
| parent | 77b096b5f2a0becf5ed578f9a5dea854fda8c05b (diff) | |
| download | perl-af685957336d0a37645ff959496386c489e0b52a.tar.gz | |
reentrant buffers
Message-ID: <20020926220856.GA339120@lyta.hut.fi>
p4raw-id: //depot/perl@17967
Diffstat (limited to 'pod/perlthrtut.pod')
| -rw-r--r-- | pod/perlthrtut.pod | 13 |
1 files changed, 9 insertions, 4 deletions
diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index cafcbb21a6..575ec27c52 100644 --- a/pod/perlthrtut.pod +++ b/pod/perlthrtut.pod @@ -1016,10 +1016,15 @@ calls, they will be used. Beyond that, Perl is at the mercy of the thread-safety or -unsafety of the calls. Please consult your C library call documentation. -In some platforms the thread-safe interfaces may fail if the result -buffer is too small (for example getgrent() may return quite large -group member lists). Perl will retry growing the result buffer -a few times, but only up to 64k (for safety reasons). +On some platforms the thread-safe library interfaces may fail if the +result buffer is too small (for example the user group databases may +be rather large, and the reentrant interfaces may have to carry around +a full snapshot of those databases). Perl will start with a small +buffer, but keep retrying and growing the result buffer +until the result fits. If this limitless growing sounds bad for +security or memory consumption reasons you can recompile Perl with +PERL_REENTRANT_MAXSIZE defined to the maximum number of bytes you will +allow. =head1 Conclusion |