From: Alex Netes <alexne-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Or Gerlitz <ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Vladimir Sokolovsky
<vlad-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
Roi Dayan <roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: opensm logs can go anywhere in size?
Date: Fri, 8 Jul 2011 12:20:30 +0300 [thread overview]
Message-ID: <20110708092030.GA7420@calypso.voltaire.com> (raw)
In-Reply-To: <4E157735.1040901-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Hi Or,
On 12:07 Thu 07 Jul , Or Gerlitz wrote:
> Hi Alex,
>
> I just noted that opensm logs can go anywhere in size when one of my
> nodes had no space left on device after the opensm log level was raised...
>
> I see that the rpm provided with RHEL6 is setting an
> /etc/logrotate.d/opensm
> entry which is a copy of ./scripts/opensm.logrotate from the opensm
> git saying
>
> /var/log/opensm.log {
> missingok
> notifempty
> copytruncate
> weekly
> compress
> }
>
> this lacks size limitation, isn't that?
>
> I opened ofa bz ticket #2280 to track that,
>
It's a good point. What should be the limit? 1MB, 10MB, 100MB? How many
history files (rotate) should be kept?
Moreover, this flooding would also happen if you don't enable logroatate, so
should we enable some default limit to opensm log (--log_limit)?
-- Alex.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-07-08 9:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 9:07 opensm logs can go anywhere in size? Or Gerlitz
[not found] ` <4E157735.1040901-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2011-07-08 9:20 ` Alex Netes [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=20110708092030.GA7420@calypso.voltaire.com \
--to=alexne-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ogerlitz-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=roid-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=vlad-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.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