supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: supervision@list.skarnet.org
Subject: Re: >2G file support for svlogd?
Date: Wed, 19 Jun 2013 14:10:43 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.1306191408480.25589@e-smith.charlieb.ott.istop.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1306191404140.25589@e-smith.charlieb.ott.istop.com>


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'.

[root@dl360p-g8 ~]# for i in $(seq 1 1048576) ; do cat /tmp/psfax ; done | 
strace -s4000 -o/tmp/svlogd.trace ./usr/bin/svlogd -t /var/log/logtest/^C
...
svlogd: pausing: unable to write to current: /var/log/logtest/: file too 
big
svlogd: pausing: unable to write to current: /var/log/logtest/: file too 
big
svlogd: pausing: unable to write to current: /var/log/logtest/: file too 
big
^C
[root@dl360p-g8 ~]# grep LARGE /tmp/svlogd.trace
open(".", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY|O_CLOEXEC) = 6
[root@dl360p-g8 ~]# 
[root@dl360p-g8 ~]# grep current /tmp/svlogd.trace 
stat64("current", {st_mode=S_IFREG|0644, st_size=2147483647, ...}) = 0
rename("current", "@4000000051afe936084b38ec.u") = 0
open("current", O_WRONLY|O_CREAT|O_APPEND|O_NONBLOCK, 0600) = 6
^C
[root@dl360p-g8 ~]# 


  reply	other threads:[~2013-06-19 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-19 18:07 Charlie Brady
2013-06-19 18:10 ` Charlie Brady [this message]
2013-06-19 18:58   ` Solved (Re: >2G file support for svlogd?) Charlie Brady

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.1306191408480.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).