LARGEFILE_SUPPORT (fwd)
Carter Bullard
carter at qosient.com
Fri Nov 9 12:46:02 EST 2001
Hey Martin,
I'm going to add a linux 2.4 or higher test, and
then I was thinking of using an autoconf macro
to test if lseek64() existed when I make the appropriate
defines.
Is lseek64() a reasonable tag, or do you think
there is a better one?
Carter
Carter Bullard
QoSient, LLC
300 E. 56th Street, Suite 18K
New York, New York 10022
carter at qosient.com
Phone +1 212 588-9133
Fax +1 212 588-9134
http://qosient.com
> -----Original Message-----
> From: Martin Siegert [mailto:siegert at sfu.ca]
> Sent: Thursday, November 08, 2001 1:47 PM
> To: Peter Van Epp
> Cc: carter at qosient.com; scott at xs4all.nl; argus at lists.andrew.cmu.edu
> Subject: Re: LARGEFILE_SUPPORT (fwd)
>
>
> LFS support is in Linux since the 2.4 kernels and glibc 2.2
> came out. It should work out of the box. This is on a RedHat
> 7.2 box using the new ext3 journaling filesystem and a
> linux-2.4.13-ac4 kernel:
>
> # dd if=/dev/zero of=./largefile bs=1M count=5120
> 5120+0 records in
> 5120+0 records out
> # ls -l largefile
> -rw-r--r-- 1 siegert users 5368709120 Nov 8 10:30 largefile
>
> You can actually get LFS support for Linux even on a 2.2
> system with glibc 2.1: The "enterprise" version of the RedHat
> kernel (e.g., kernel-enterprise-2.2.19-6.2.12.i686.rpm) has
> LFS support for RedHat 6.2 as well.
>
> I hope this helps.
>
> Martin
>
> ==============================================================
> ==========
> Martin Siegert
> Academic Computing Services phone:
> (604) 291-4691
> Simon Fraser University fax:
> (604) 291-4242
> Burnaby, British Columbia email:
> siegert at sfu.ca
> Canada V5A 1S6
> ==============================================================
> ==========
>
> On Thu, Nov 08, 2001 at 07:41:13AM -0800, Peter Van Epp wrote:
> > Martin:
> > Being the local expert do you have any suggestions on
> this? They are
> > trying to get 64 bit file pointers in a linux XFS system
> for greater
> > than 2 gig files and need a configure flag that will determine the
> > kernel can do it.
> >
> > Peter Van Epp / Operations and Technical Support
> >
> > Forwarded message:
> > > From owner-argus-info at lists.andrew.cmu.edu Thu Nov 8
> 06:59:29 2001
> > > X-pair-Authenticated: 162.83.194.45
> > > Reply-To: <carter at qosient.com>
> > > From: "Carter Bullard" <carter at qosient.com>
> > > To: <carter at qosient.com>, "'Scott A. McIntyre'" <scott at xs4all.nl>
> > > Cc: "'Argus Mailing List'" <argus at lists.andrew.cmu.edu>
> > > Subject: LARGEFILE_SUPPORT
> > > Date: Thu, 8 Nov 2001 09:59:15 -0500
> > > Organization: QoSient, LLC
> > > Message-ID:
> > > <5C8959A16A71B449AE793CF52FBBED6603BCD4 at ptah.newyork.qosient.com>
> > > MIME-Version: 1.0
> > > Content-Type: text/plain;
> > > charset="US-ASCII"
> > > Content-Transfer-Encoding: 7bit
> > > X-Priority: 3 (Normal)
> > > X-MSMail-Priority: Normal
> > > X-Mailer: Microsoft Outlook, Build 10.0.3311
> > > X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
> > > In-Reply-To:
> <5C8959A16A71B449AE793CF52FBBED6603BCBD at ptah.newyork.qosient.com>
> > > Importance: Normal
> > > Sender: owner-argus-info at lists.andrew.cmu.edu
> > > Precedence: bulk
> > > Content-Length: 2096
> > >
> > > Hey Gentle people,
> > > Do we have any concensus as to how to put this
> > > support into Linux? I haven't found any autoconf
> > > macros for whether a system supports large files.
> > >
> > > Do we just turn it on anyway, and see what happens?
> > >
> > > Carter
> > >
> > > Carter Bullard
> > > QoSient, LLC
> > > 300 E. 56th Street, Suite 18K
> > > New York, New York 10022
> > >
> > > carter at qosient.com
> > > Phone +1 212 588-9133
> > > Fax +1 212 588-9134
> > > http://qosient.com
> > >
> > > > -----Original Message-----
> > > > From: owner-argus-info at lists.andrew.cmu.edu
> > > > [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of
> > > > Carter Bullard
> > > > Sent: Friday, November 02, 2001 5:48 PM
> > > > To: 'Scott A. McIntyre'
> > > > Cc: 'Argus Mailing List'
> > > > Subject: RE: argusarchive.
> > > >
> > > >
> > > > Hey Scott,
> > > > Well the changes I put in are important, but the
> > > > (2^31 - 1) sure looks like a real binary clue, if
> > > > I ever saw one. Not much we can do if the system
> > > > routine dumps core in this situation.
> > > >
> > > > We can put in a file size parameter and not generate files
> > > > bigger than x, if that is the only solution.
> > > >
> > > > Carter
> > > >
> > > > Carter Bullard
> > > > QoSient, LLC
> > > > 300 E. 56th Street, Suite 18K
> > > > New York, New York 10022
> > > >
> > > > carter at qosient.com
> > > > Phone +1 212 588-9133
> > > > Fax +1 212 588-9134
> > > > http://qosient.com
> > > >
> > > > > -----Original Message-----
> > > > > From: owner-argus-info at lists.andrew.cmu.edu
> > > > > [mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of
> > > > > Scott A. McIntyre
> > > > > Sent: Friday, November 02, 2001 3:29 PM
> > > > > To: Carter Bullard
> > > > > Cc: 'Argus Mailing List'
> > > > > Subject: Re: argusarchive.
> > > > >
> > > > >
> > > > > > Yes I found a set of problems relating to writing out
> > > > > > queued records when the file has been removed. I've fixed
> > > > > > them in
> > > > > the 2.0.4
> > > > > > code that is in the test directory.
> > > > > >
> > > > > > ftp://qosient.com/dev/argus-2.0/argus-2.0.4.beta.1.tar.gz
> > > > > >
> > > > > > Could you give this a try?
> > > > >
> > > > > Yep, trying it now -- one other interesting point
> that will no
> > > > > doubt confuse the matter. I removed the argusarchive cron
> > > > > script entirely, and it still died. File size is 2147483647
> > > > > bytes, 86086413 packets..
> > > > >
> > > > > Scott
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
>
>
More information about the argus
mailing list