[cs615asa] hw5 Question

[Justin Barish]

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).
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?

Also, should we have du count filesystem mount points, or ignore them (-x
flag)?

-Justin

On Wed, Apr 3, 2019 at 9:13 PM Jan Schaumann <jschauma at stevens.edu> wrote:

> Robert Herley IV <rherley at stevens.edu> wrote:
> > Should we limit our EBS volume type to be just standard? If so, our
> backup
> > limit would be 1,024 GiB.
>
> That's fine.
>
> > Also, do we need to worry about symbolic links when backing up?
>
> You don't have to worry about any of the file attributes or properties;
> tar(1) handles all of that for you.
>
> -Jan
> _______________________________________________
> cs615asa mailing list
> cs615asa at lists.stevens.edu
> https://lists.stevens.edu/mailman/listinfo/cs615asa
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.stevens.edu/pipermail/cs615asa/attachments/20190403/22f214fd/attachment.html>