> What will happen to me if I write more complicated shell scripts?
As part of my job currently, I am going to delete it.
The same goes for poor python code, but I will take bad python over shell scripts any day of the week.
As part of my job currently, I am going to delete it.
The same goes for poor python code, but I will take bad python over shell scripts any day of the week.
Go away, or I will turn you into a very small shell script.
#!/bin/bash
find / -name \*.sh -size +10k -type f -print0 | xargs -0 rm $ mangle find -delete
ACTIONS
-delete
Delete files; true if removal succeeded. If the removal failed, an error message is issued. If -delete fails, find's exit status will be nonzero (when it eventually exits). Use of -delete automatically turns on the
-depth option.
Warnings: Don't forget that the find command line is evaluated as an expression, so putting -delete first will make find try to delete everything below the starting points you specified. When testing a find command line
that you later intend to use with -delete, you should explicitly specify -depth in order to avoid later surprises. Because -delete implies -depth, you cannot usefully use -prune and -delete together.