From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: supervision@list.skarnet.org
Subject: Solved (Re: >2G file support for svlogd?)
Date: Wed, 19 Jun 2013 14:58:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1306191457350.25589@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306191408480.25589@e-smith.charlieb.ott.istop.com>
On Wed, 19 Jun 2013, Charlie Brady wrote:
>
> On Wed, 19 Jun 2013, Charlie Brady wrote:
>
> > Has anyone built svlogd to handle large files?
>
> It looks like O_LARGEFILE is used when opening '.' but not when opening
> 'current'.
...
#Change the conf-cc and conf-ld to enable large file support
echo 'gcc -O2 -Wall -D_FILE_OFFSET_BITS=64' >src/conf-cc
echo 'gcc -s -Os -pipe' >src/conf-ld
./package/compile
...
[root@sdfds ~]# fg
for i in $(seq 1 1048576);
do
cat /tmp/psfax;
done | ./usr/bin/svlogd -t /var/tmp/log/
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
...
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
svlogd: pausing: unable to write to current: /var/tmp/log/: out of disk
space
^C
[root@sdfds ~]#
[root@sdfds ~]# ls -l /var/tmp/log
total 3532880
-rw-r--r-- 1 root root 10 Jun 15 19:11 config
-rw-r--r-- 1 root root 3614130176 Jun 15 19:24 current
-rw------- 1 root root 0 Jun 15 19:12 lock
[root@sdfds ~]#
prev parent reply other threads:[~2013-06-19 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 18:07 >2G file support for svlogd? Charlie Brady
2013-06-19 18:10 ` Charlie Brady
2013-06-19 18:58 ` Charlie Brady [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.1306191457350.25589@e-smith.charlieb.ott.istop.com \
--to=charlieb-supervision@budge.apana.org.au \
--cc=supervision@list.skarnet.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 NNTP newsgroup(s).