Answer by Alex for ls: terminated by signal 13 when using xargs
I suggest to find and destroy "xargs" when "head" job is done$ cat /tmp/50m.txt | xargs -n1 echo | { head -n2; kill -2 $(pidof xargs); }; echo "${PIPESTATUS[*]}"141 130 0130 return code shows that...
View ArticleAnswer by mattalxndr for ls: terminated by signal 13 when using xargs
One way to avoid this is to switch head for perl -ne.Starting with your original command:find "/var/www/site1/" -maxdepth 1 -type f | xargs ls -1S | head -n 4 | xargs -d '\n' rm -fAs you've probably...
View ArticleAnswer by gws for ls: terminated by signal 13 when using xargs
I got the same error, "terminated by signal 13", under different circumstances and other answers here helped me work out the fix. I'd like to expand on the nature of the problem:corpy386...
View ArticleAnswer by David Espart for ls: terminated by signal 13 when using xargs
You are purposely terminating your program with head -n 4, which creates the broken pipe because you terminated it before the "caller" finished. Since this is expected by you, you can ignore the error...
View ArticleAnswer by planetmaker for ls: terminated by signal 13 when using xargs
I ran across a similar issue and found this thread on search for an answer:Signal 13 means something is written to a pipe where nothing is read from anymore (e.g. see...
View Articlels: terminated by signal 13 when using xargs
I'm using the following command to delete four largest size files in a folder:find "/var/www/site1/" -maxdepth 1 -type f | xargs ls -1S | head -n 4 | xargs -d '\n' rm -fIt works fine, but from time to...
View Article
