<div dir="ltr"><div dir="ltr">The du function often returns errors/warnings about certain directories that cannot be read if the user tries to run du on '/' (such as du: /proc/2093/fd/8: No such file or directory). </div><div dir="ltr">Since we should check the return code of all functions for failure, how should this be handled, since the above causes a return code of 1, as does other possible failures? Would a correct answer be to just ignore the return value of du, and do checks (such as the existence of the directory) separately?</div><div dir="ltr"><br></div><div>Also, should we have du count filesystem mount points, or ignore them (-x flag)?</div><div><br></div><div>-Justin</div><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 3, 2019 at 9:13 PM Jan Schaumann <<a href="mailto:jschauma@stevens.edu">jschauma@stevens.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Robert Herley IV <<a href="mailto:rherley@stevens.edu" target="_blank">rherley@stevens.edu</a>> wrote:<br>
> Should we limit our EBS volume type to be just standard? If so, our backup<br>
> limit would be 1,024 GiB.<br>
<br>
That's fine.<br>
<br>
> Also, do we need to worry about symbolic links when backing up?<br>
<br>
You don't have to worry about any of the file attributes or properties;<br>
tar(1) handles all of that for you.<br>
<br>
-Jan<br>
_______________________________________________<br>
cs615asa mailing list<br>
<a href="mailto:cs615asa@lists.stevens.edu" target="_blank">cs615asa@lists.stevens.edu</a><br>
<a href="https://lists.stevens.edu/mailman/listinfo/cs615asa" rel="noreferrer" target="_blank">https://lists.stevens.edu/mailman/listinfo/cs615asa</a><br>
</blockquote></div>