<div dir="auto">If there is another, bigger system on the local network, you can always syslog the logs to that. That's what it was designed for.</div><br><div class="gmail_quote"><div dir="ltr">On Thu, 13 Dec 2018, 18:27 Robert Moskowitz <<a href="mailto:rgm@htt-consult.com">rgm@htt-consult.com</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<br>
<br>
<div class="m_-7868424869932941706moz-cite-prefix">On 12/13/18 12:09 PM, Fred Gleason
wrote:<br>
</div>
<blockquote type="cite">
On Dec 13, 2018, at 11:54, Stephan Guilloux <<a href="mailto:stephan.guilloux@crisalid.com" target="_blank" rel="noreferrer">stephan.guilloux@crisalid.com</a>>
wrote:
<div><br>
<div>
<blockquote type="cite">
<div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);float:none;display:inline!important">Stress test still
running on reputable brand with no PB, after 6 or 7h.</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);float:none;display:inline!important">During this
stressing session, we found a few broken SD, from
another reputable brand.<span class="m_-7868424869932941706Apple-converted-space"> </span></span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);float:none;display:inline!important">Not all cards,
though, but enough to put some confusion... ;-)</span></div>
</blockquote>
</div>
<br>
</div>
<div>Well, remember, we are dealing with flash RAM here.
After enough write/erase cycles, it *will* wear out. The goal is
to optimize the overall system to get maximum lifetime out of
the media. For example, on our production setups we do things
like putting ‘/var/log’ on tmpfs (it doesn’t matter for the
particular application that the log data evaporates after
reboots). That greatly reduces wear on the media, while still
allowing log data to be accessed during a session for debug
purposes.<br>
</div>
</blockquote>
<br>
All too often I am looking at contents of /var/log after a system
restart to figure out what went wrong.<br>
<br>
So that is yet another reason I am sticking with SOCs that have good
sata support. So I can run rootfs there...<br>
<br>
<br>
</div>
_______________________________________________<br>
Arm-dev mailing list<br>
<a href="mailto:Arm-dev@centos.org" target="_blank" rel="noreferrer">Arm-dev@centos.org</a><br>
<a href="https://lists.centos.org/mailman/listinfo/arm-dev" rel="noreferrer noreferrer" target="_blank">https://lists.centos.org/mailman/listinfo/arm-dev</a><br>
</blockquote></div>