Problems of this kind, epecially with a beta release (which
Perl5.002beta1 is) should be sent to perl5-porters@nicoh.com.
I've CC'd this to them.
In article <ckincyDJAM57.8Ex@netcom.com>,
Chuck Kincy <ckincy@netcom.com> wrote:
> I have a DBM database with about 6 megabytes of actual data on
> a Solaris 2.3 box running Perl 5.002. The scripts that manipulate
> this database use the dbmopen method (rather than tie...the reason
> for this is a long story).
>
> Anyway, the DBM database .pag file reports its file size as
> 1,369,762,816 bytes. I realize that DBM files are sparse and that
> they usually report 4 times as large as they actually are, but
> this is a 200:1 ratio!
>
> The problem with this is that the database is not growing any larger
> and records are silently getting lost. My theory is that the
> database is trying to grow again and the result is larger than
> the 32-bit address space Solaris supports. But I do not know this
> for sure because I'm unable to look into the guts of the library
> to see what is going on.
>
> Has anyone else had this problem?
>
> cpk
> --
> Chuck Kincy ---------------------<*>-------------------- ckincy@netcom.com
> Dallas, TX BSCS '94 -- U of Missouri-Rolla
>
> Linux sucks, but everything else sucks more. What can one do?
Perl5.002beta1 is) should be sent to perl5-porters@nicoh.com.
I've CC'd this to them.
In article <ckincyDJAM57.8Ex@netcom.com>,
Chuck Kincy <ckincy@netcom.com> wrote:
> I have a DBM database with about 6 megabytes of actual data on
> a Solaris 2.3 box running Perl 5.002. The scripts that manipulate
> this database use the dbmopen method (rather than tie...the reason
> for this is a long story).
>
> Anyway, the DBM database .pag file reports its file size as
> 1,369,762,816 bytes. I realize that DBM files are sparse and that
> they usually report 4 times as large as they actually are, but
> this is a 200:1 ratio!
>
> The problem with this is that the database is not growing any larger
> and records are silently getting lost. My theory is that the
> database is trying to grow again and the result is larger than
> the 32-bit address space Solaris supports. But I do not know this
> for sure because I'm unable to look into the guts of the library
> to see what is going on.
>
> Has anyone else had this problem?
>
> cpk
> --
> Chuck Kincy ---------------------<*>-------------------- ckincy@netcom.com
> Dallas, TX BSCS '94 -- U of Missouri-Rolla
>
> Linux sucks, but everything else sucks more. What can one do?