|
From: | Jeff Kirkpatrick |
Subject: | `du` check for directory loop avoidance |
Date: | Wed, 18 Dec 2013 10:46:32 -0600 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120601 Thunderbird/10.0.5 |
A Red Hat customer has
registered a concern over the non-zero exit code that results when
du traverses a directory loop, i.e. a chrooted environment. The recent Red Hat Enterprise Linux 6.5 errata http://rhn.redhat.com/errata/RHSA-2013-1652.html includes a change to the warning message received (FROM "WARNING: Circular directory structure. This almost certainly means that you have a corrupted file system." TO " du: mount point `/var/named/chroot/var/named' already traversed") however there is still a non-zero exit code. Customer states "The message may be acceptable, but it shouldn't give a failure exit value for a situation that is not an error. In reading the technical notes, I see the non-zero exit code was deliberate. But I don't understand why it would be considered an error." When I reached out to our engineering organization I received the following response: "Non-zero exit code was chosen by upstream - we only followed their decision. Part of the discussion is at the http://debbugs.gnu.org/cgi/bugreport.cgi?bug=11844 and second at http://lists.gnu.org/archive/html/bug-coreutils/2010-01/msg00011.html ... However, I don't see explicit reasons for the non-zero exit code. If you want to ask for the reason, you may write an email to address@hidden."Can anyone elaborate on why the decision to use a non-zero exit code? Best Regards, Jeff Kirkpatrick, Support Relationship Manager Strategic Customer Engagement Red Hat Global Support Services For Immediate Technical Support - 1.888.GO.REDHAT (888.467.3342) |
[Prev in Thread] | Current Thread | [Next in Thread] |