Lines Matching refs:failed

7   cp, mv, and install no longer issue spurious diagnostics like "failed
54   Previously it would have failed with a "No such file or directory" error.
168   it failed to appropriately rename files being replaced.
243   Previously it may have aborted with a failed assertion in some cases.
1765   mount points.  Previously it may have failed to output some mount points.
1777   install now removes the target file if the strip program failed for any
2613   du would abort with a failed assertion when two conditions are met:
3115   from a failed stat/lstat.  For example ls -Lis now prints "?", not "0",
3260   truncate -s failed to skip all whitespace in the option argument in
4797     incorrect, as it failed to update the last-changed time and reset
4893   rm no longer gets a failed assertion under some unusual conditions.
5501 * du no longer gets a failed assertion for certain hierarchy lay-outs
5724     127 if nohup failed or if command was not found.