From: sadasiva.reddy@gmail.com (SADA SIVA REDDY S)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to limit the total size used by core files or automatically delete old corefiles.
Date: Fri, 27 May 2011 09:11:35 +0100 [thread overview]
Message-ID: <BANLkTi=fbPnVjdn=P3bM6D6nUg-eh6dC+A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikXYafYMQkQ3sJgaLZv9hgCbYs+JA@mail.gmail.com>
Thanks Andrej and Manish.
I will try to see if I can use logrotat or atleast buy the logic from it.
Thanks,
SADA
On Thu, May 26, 2011 at 10:55 PM, Manish Katiyar <mkatiyar@gmail.com> wrote:
> On Thu, May 26, 2011 at 5:31 AM, SADA SIVA REDDY S
> <sadasiva.reddy@gmail.com> wrote:
> > Hi All,
> > I have a situation like below. I am using RHEL 5.
> >
> > I have multiple user processes running on my machine.
> > I have set the appropriate sizes for core file size.
> > But my process maangement demon is designed to restart any process that
> > terminates.
> > Hence the process starts up again.
> > If I have a very bad nasty defect, it will keep on filling my machine
> with
> > core files until I run out of space on the partition.
> >
> > My Questions:
> >
> > Is there a provision in Linux to automatically cleanup the old corefiles
> > when we reach a certain limit ?
> > Is there a provision in Linux to set a upper limit for space occupied by
> all
> > core files (not individual core files) ?
> >
> > Any inputs appreciated.
>
> May be "man logrotate" can help.
>
> --
> Thanks -
> Manish
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110527/a4d8edad/attachment.html
prev parent reply other threads:[~2011-05-27 8:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 12:31 How to limit the total size used by core files or automatically delete old corefiles SADA SIVA REDDY S
2011-05-26 16:05 ` Andrzej Kardas
2011-05-26 21:55 ` Manish Katiyar
2011-05-27 8:11 ` SADA SIVA REDDY S [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='BANLkTi=fbPnVjdn=P3bM6D6nUg-eh6dC+A@mail.gmail.com' \
--to=sadasiva.reddy@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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).