From: Charlie Brady <charlieb-supervision@budge.apana.org.au>
To: supervision@list.skarnet.org
Subject: >2G file support for svlogd?
Date: Wed, 19 Jun 2013 14:07:27 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.1306191404140.25589@e-smith.charlieb.ott.istop.com> (raw)
Has anyone built svlogd to handle large files?
If svlogd is set up for time based log rotation:
s0
t86400
with a very verbose service, then we see:
nanosleep({3, 0}, 0xbf9a245c) = 0
write(6, "rverCore.setThreadName: (ServerCore.java:96) Renamed thread
to UspService-InternalServer-ServerMain\n", 100) = -1 EFBIG (File too
large)
write(2, "svlogd: pausing: unable to write to current:
/var/log/mom-server: file too big\n", 79) = 79
..so it's trying to write, getting EFBIG, sleeping, trying to write etc...
next reply other threads:[~2013-06-19 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 18:07 Charlie Brady [this message]
2013-06-19 18:10 ` Charlie Brady
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.1306191404140.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).