Very Computer

> Apache is not able to write logfiles larger than 2 GB isn't it ?
> How can I get Apache to do so.
> Is it possible to filter the logging from Apache during running from
> Apache so that Logentries with *xyz* will not be logged. How.
> The documentation on this is too small. I cannot test to much, because I
> need this Feature on a highly used machine. (Now about 2 GB Logfile in
> 16 hours)

> Thanks in advance!

> Regards Marcus

> The IMO only and fastest way is to rotate your log e.g. each
> hour and avoid the 2GB boundary.

> Perhaps someone can tell if this problem is fixed in Solaris 2.7...

> - rainer

> > Apache is not able to write logfiles larger than 2 GB isn't it ?
> > How can I get Apache to do so.
> > Is it possible to filter the logging from Apache during running from
> > Apache so that Logentries with *xyz* will not be logged. How.
> > The documentation on this is too small. I cannot test to much, because I
> > need this Feature on a highly used machine. (Now about 2 GB Logfile in
> > 16 hours)

> > Thanks in advance!

> > Regards Marcus

> Thank you for your ideas, but:

> Here you see the documentation about solaris from sun.

> Copyright (c) 1997 Sun Microsystems, Inc.

> DOCUMENT ID: 2480-02

> SYNOPSIS:    Maximum single file and file system size

> OS:          Solaris/SunOS

> PLATFORM:    Generic

> OS VERSION:  2.6

> TECH AREA:   OS

> PRODUCT:     Kernel

> KEYWORDS:    large, size, single, fs

> DESCRIPTION:

> What's the maximum single file and file system size supported in Solaris
> 2.5.1, 2.6 ?

> SOLUTION:

> This lists the maximum single file and file system size of 4.1.x and Solaris
> 2.x up to 2.6.

> OS RELEASE              SINGLE FILE             FILE SYSTEM
> ===============         ===========             ===========
> 4.1.x                      2 GB                     2 GB
> 4.1.x + ODS                2 GB                     1 TB
> Solaris 2.0-2.5.1          2 GB                     1 TB
> Solaris 2 + SDS            2 GB                     1 TB
> Solaris 2.6                ~800 GB                  1 TB

> A single file of Solaris 2.6 is limited to "about" 800 GB because the file
> MUST fit inside a file system. The file system is nominally 1 TB, but in fact
> one must create enough overhead in such a large file system that the largest
> single file ends up being "about" 800 GB. (part of this is a bug, but even if
> bug-free a single file can't be 1 TB)

> Note that in Solaris 2.6, the swap and tmpfs file system are still limited to
> 2 GB.  Also note that the root file system is limited to ~2 GB on all but
> Ultras due to an OBP limitation (~1 GB on systems with OBP versions 1.0->2.6).

> ---------------------------------------------------------------

> So I think that this should be no problem of solaris

> The rotating of the log is of course possible but in our case more komplex for
> further actions.

> Marcus

> Rainer Scherg schrieb:

> > That's not possible for apache.
> > Because this is a Solaris OS problem.

> > The IMO only and fastest way is to rotate your log e.g. each
> > hour and avoid the 2GB boundary.

> > Perhaps someone can tell if this problem is fixed in Solaris 2.7...

> > - rainer

> > > Apache is not able to write logfiles larger than 2 GB isn't it ?
> > > How can I get Apache to do so.
> > > Is it possible to filter the logging from Apache during running from
> > > Apache so that Logentries with *xyz* will not be logged. How.
> > > The documentation on this is too small. I cannot test to much, because I
> > > need this Feature on a highly used machine. (Now about 2 GB Logfile in
> > > 16 hours)

> > > Thanks in advance!

> > > Regards Marcus

>That isn't an Apache issue, but a Solaris one.  If you compile Apache
>with the right magic flags for large file support it likely would work.