Who is eating data? Xargs?2019 Community Moderator ElectionXargs and rm with a *What's wrong with this xargs command?Piping nothing to xargsxargs -r0 vs xargs -0Format output of xargsxargs line too longechoing basename under xargs?Combining bash % with xargs %xargs -I optionBenefits of using xargs

BitNot does not flip bits in the way I expected

How strictly should I take "Candidates must be local"?

How to create a hard link to an inode (ext4)?

Should I take out a loan for a friend to invest on my behalf?

What is the likely impact of grounding an entire aircraft series?

Good allowance savings plan?

How does airport security verify that you can carry a battery bank over 100 Wh?

Make a transparent 448*448 image

Solving "Resistance between two nodes on a grid" problem in Mathematica

Am I not good enough for you?

Why doesn't this Google Translate ad use the word "Translation" instead of "Translate"?

My story is written in English, but is set in my home country. What language should I use for the dialogue?

Could a cubesat propel itself to Mars?

Why the color red for the Republican Party

What are the pros and cons of practising figure-eight landings on perpendicular runways?

Should I tell my boss the work he did was worthless

Fourth person (in Slavey language)

Is Gradient Descent central to every optimizer?

Who deserves to be first and second author? PhD student who collected data, research associate who wrote the paper or supervisor?

Do f-stop and exposure time perfectly cancel?

A question on the ultrafilter number

Is "history" a male-biased word ("his+story")?

What to do when during a meeting client people start to fight (even physically) with each others?

How do I deal with a powergamer in a game full of beginners in a school club?



Who is eating data? Xargs?



2019 Community Moderator ElectionXargs and rm with a *What's wrong with this xargs command?Piping nothing to xargsxargs -r0 vs xargs -0Format output of xargsxargs line too longechoing basename under xargs?Combining bash % with xargs %xargs -I optionBenefits of using xargs










2















I am trying to parse a recursive directory of PHP files using the built in PHP linter, which works like this:



$ php -l good.php
No syntax errors detected in good.php

$ php -l bad.php
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


We can see that files which pass linting output a line containing No syntax errors and those which fail linting output a line containing Errors parsing.



I see that I have 12147 PHP files recursively in the current directory, however the PHP linter is only outputting seven lines:



$ find . -name *.php -print0 | xargs -0 ls -l | wc -l
12147

$ find . -name *.php -print0 | xargs -0 php -l | wc -l
7


As there were only 7 files parsed by PHP, I can use my head with ls to find some files which have not been parsed:



$ find . -name *.php -print0 | xargs -0 ls -l | head
-rw-r--r-- 1 dotan dotan 1927 Jan 13 10:13 ./bootstrap/app.php
-rw-r--r-- 1 dotan dotan 1076 Jan 13 10:13 ./bootstrap/autoload.php
-rw-rw-r-- 1 dotan dotan 25620 Mar 12 12:29 ./bootstrap/cache/services.php
-rw-r--r-- 1 dotan dotan 2493 Jan 13 10:13 ./bootstrap/paths.php
-rwxrwxr-x 1 dotan dotan 20008 Mar 12 12:30 ./config/app.php
-rw-r--r-- 1 dotan dotan 3304 Jan 13 10:13 ./config/auth.php
-rw-r--r-- 1 dotan dotan 1819 Jan 13 10:13 ./config/cache.php
-rw-r--r-- 1 dotan dotan 3751 Jan 13 10:13 ./config/cartalyst.sentinel-addons.social.php
-rw-r--r-- 1 dotan dotan 6849 Jan 13 10:13 ./config/cartalyst.sentinel.php
-rw-r--r-- 1 dotan dotan 1020 Jan 13 10:13 ./config/compile.php
xargs: ls: terminated by signal 13

$ find . -name *.php -print0 | xargs -0 php -l
No syntax errors detected in ./bootstrap/paths.php
No syntax errors detected in ./vendor/watson/validating/src/ValidatingTrait.php
No syntax errors detected in ./vendor/giggsey/libphonenumber-for-php/src/libphonenumber/data/PhoneNumberMetadata_SI.php
No syntax errors detected in ./vendor/php-vcr/php-vcr/src/VCR/Event/BeforePlaybackEvent.php
No syntax errors detected in ./vendor/laravel/framework/src/Illuminate/Support/Facades/Blade.php
No syntax errors detected in ./resources/views/emails/appointment/updated/body.blade.php
No syntax errors detected in ./app/WL/Modules/Location/Commands/RemoveClientLocationCommand.php


Yet, when I try to parse one of those files I see that it does produce the expected output (either passing or failing parsing):



$ php -l ./bootstrap/cache/services.php
No syntax errors detected in ./bootstrap/cache/services.php


I've checked that neither passing nor failing linting is printing the expected lines to stderr:



$ php -l good.php | grep rr
No syntax errors detected in good.php

$ php -l bad.php | grep rr
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


What should I check now? My end goal is to lint all the files, then grep for Error parsing to fix those issues.










share|improve this question

















  • 1





    Can the php -l command take multiple arguments with the syntax php -l file1 file2 file3? xargs would be passing the results of find in batches.

    – Haxiel
    14 hours ago











  • @Haxiel: Thank you, in fact xargs was batching. Learn something every day!

    – dotancohen
    14 hours ago















2















I am trying to parse a recursive directory of PHP files using the built in PHP linter, which works like this:



$ php -l good.php
No syntax errors detected in good.php

$ php -l bad.php
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


We can see that files which pass linting output a line containing No syntax errors and those which fail linting output a line containing Errors parsing.



I see that I have 12147 PHP files recursively in the current directory, however the PHP linter is only outputting seven lines:



$ find . -name *.php -print0 | xargs -0 ls -l | wc -l
12147

$ find . -name *.php -print0 | xargs -0 php -l | wc -l
7


As there were only 7 files parsed by PHP, I can use my head with ls to find some files which have not been parsed:



$ find . -name *.php -print0 | xargs -0 ls -l | head
-rw-r--r-- 1 dotan dotan 1927 Jan 13 10:13 ./bootstrap/app.php
-rw-r--r-- 1 dotan dotan 1076 Jan 13 10:13 ./bootstrap/autoload.php
-rw-rw-r-- 1 dotan dotan 25620 Mar 12 12:29 ./bootstrap/cache/services.php
-rw-r--r-- 1 dotan dotan 2493 Jan 13 10:13 ./bootstrap/paths.php
-rwxrwxr-x 1 dotan dotan 20008 Mar 12 12:30 ./config/app.php
-rw-r--r-- 1 dotan dotan 3304 Jan 13 10:13 ./config/auth.php
-rw-r--r-- 1 dotan dotan 1819 Jan 13 10:13 ./config/cache.php
-rw-r--r-- 1 dotan dotan 3751 Jan 13 10:13 ./config/cartalyst.sentinel-addons.social.php
-rw-r--r-- 1 dotan dotan 6849 Jan 13 10:13 ./config/cartalyst.sentinel.php
-rw-r--r-- 1 dotan dotan 1020 Jan 13 10:13 ./config/compile.php
xargs: ls: terminated by signal 13

$ find . -name *.php -print0 | xargs -0 php -l
No syntax errors detected in ./bootstrap/paths.php
No syntax errors detected in ./vendor/watson/validating/src/ValidatingTrait.php
No syntax errors detected in ./vendor/giggsey/libphonenumber-for-php/src/libphonenumber/data/PhoneNumberMetadata_SI.php
No syntax errors detected in ./vendor/php-vcr/php-vcr/src/VCR/Event/BeforePlaybackEvent.php
No syntax errors detected in ./vendor/laravel/framework/src/Illuminate/Support/Facades/Blade.php
No syntax errors detected in ./resources/views/emails/appointment/updated/body.blade.php
No syntax errors detected in ./app/WL/Modules/Location/Commands/RemoveClientLocationCommand.php


Yet, when I try to parse one of those files I see that it does produce the expected output (either passing or failing parsing):



$ php -l ./bootstrap/cache/services.php
No syntax errors detected in ./bootstrap/cache/services.php


I've checked that neither passing nor failing linting is printing the expected lines to stderr:



$ php -l good.php | grep rr
No syntax errors detected in good.php

$ php -l bad.php | grep rr
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


What should I check now? My end goal is to lint all the files, then grep for Error parsing to fix those issues.










share|improve this question

















  • 1





    Can the php -l command take multiple arguments with the syntax php -l file1 file2 file3? xargs would be passing the results of find in batches.

    – Haxiel
    14 hours ago











  • @Haxiel: Thank you, in fact xargs was batching. Learn something every day!

    – dotancohen
    14 hours ago













2












2








2








I am trying to parse a recursive directory of PHP files using the built in PHP linter, which works like this:



$ php -l good.php
No syntax errors detected in good.php

$ php -l bad.php
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


We can see that files which pass linting output a line containing No syntax errors and those which fail linting output a line containing Errors parsing.



I see that I have 12147 PHP files recursively in the current directory, however the PHP linter is only outputting seven lines:



$ find . -name *.php -print0 | xargs -0 ls -l | wc -l
12147

$ find . -name *.php -print0 | xargs -0 php -l | wc -l
7


As there were only 7 files parsed by PHP, I can use my head with ls to find some files which have not been parsed:



$ find . -name *.php -print0 | xargs -0 ls -l | head
-rw-r--r-- 1 dotan dotan 1927 Jan 13 10:13 ./bootstrap/app.php
-rw-r--r-- 1 dotan dotan 1076 Jan 13 10:13 ./bootstrap/autoload.php
-rw-rw-r-- 1 dotan dotan 25620 Mar 12 12:29 ./bootstrap/cache/services.php
-rw-r--r-- 1 dotan dotan 2493 Jan 13 10:13 ./bootstrap/paths.php
-rwxrwxr-x 1 dotan dotan 20008 Mar 12 12:30 ./config/app.php
-rw-r--r-- 1 dotan dotan 3304 Jan 13 10:13 ./config/auth.php
-rw-r--r-- 1 dotan dotan 1819 Jan 13 10:13 ./config/cache.php
-rw-r--r-- 1 dotan dotan 3751 Jan 13 10:13 ./config/cartalyst.sentinel-addons.social.php
-rw-r--r-- 1 dotan dotan 6849 Jan 13 10:13 ./config/cartalyst.sentinel.php
-rw-r--r-- 1 dotan dotan 1020 Jan 13 10:13 ./config/compile.php
xargs: ls: terminated by signal 13

$ find . -name *.php -print0 | xargs -0 php -l
No syntax errors detected in ./bootstrap/paths.php
No syntax errors detected in ./vendor/watson/validating/src/ValidatingTrait.php
No syntax errors detected in ./vendor/giggsey/libphonenumber-for-php/src/libphonenumber/data/PhoneNumberMetadata_SI.php
No syntax errors detected in ./vendor/php-vcr/php-vcr/src/VCR/Event/BeforePlaybackEvent.php
No syntax errors detected in ./vendor/laravel/framework/src/Illuminate/Support/Facades/Blade.php
No syntax errors detected in ./resources/views/emails/appointment/updated/body.blade.php
No syntax errors detected in ./app/WL/Modules/Location/Commands/RemoveClientLocationCommand.php


Yet, when I try to parse one of those files I see that it does produce the expected output (either passing or failing parsing):



$ php -l ./bootstrap/cache/services.php
No syntax errors detected in ./bootstrap/cache/services.php


I've checked that neither passing nor failing linting is printing the expected lines to stderr:



$ php -l good.php | grep rr
No syntax errors detected in good.php

$ php -l bad.php | grep rr
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


What should I check now? My end goal is to lint all the files, then grep for Error parsing to fix those issues.










share|improve this question














I am trying to parse a recursive directory of PHP files using the built in PHP linter, which works like this:



$ php -l good.php
No syntax errors detected in good.php

$ php -l bad.php
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


We can see that files which pass linting output a line containing No syntax errors and those which fail linting output a line containing Errors parsing.



I see that I have 12147 PHP files recursively in the current directory, however the PHP linter is only outputting seven lines:



$ find . -name *.php -print0 | xargs -0 ls -l | wc -l
12147

$ find . -name *.php -print0 | xargs -0 php -l | wc -l
7


As there were only 7 files parsed by PHP, I can use my head with ls to find some files which have not been parsed:



$ find . -name *.php -print0 | xargs -0 ls -l | head
-rw-r--r-- 1 dotan dotan 1927 Jan 13 10:13 ./bootstrap/app.php
-rw-r--r-- 1 dotan dotan 1076 Jan 13 10:13 ./bootstrap/autoload.php
-rw-rw-r-- 1 dotan dotan 25620 Mar 12 12:29 ./bootstrap/cache/services.php
-rw-r--r-- 1 dotan dotan 2493 Jan 13 10:13 ./bootstrap/paths.php
-rwxrwxr-x 1 dotan dotan 20008 Mar 12 12:30 ./config/app.php
-rw-r--r-- 1 dotan dotan 3304 Jan 13 10:13 ./config/auth.php
-rw-r--r-- 1 dotan dotan 1819 Jan 13 10:13 ./config/cache.php
-rw-r--r-- 1 dotan dotan 3751 Jan 13 10:13 ./config/cartalyst.sentinel-addons.social.php
-rw-r--r-- 1 dotan dotan 6849 Jan 13 10:13 ./config/cartalyst.sentinel.php
-rw-r--r-- 1 dotan dotan 1020 Jan 13 10:13 ./config/compile.php
xargs: ls: terminated by signal 13

$ find . -name *.php -print0 | xargs -0 php -l
No syntax errors detected in ./bootstrap/paths.php
No syntax errors detected in ./vendor/watson/validating/src/ValidatingTrait.php
No syntax errors detected in ./vendor/giggsey/libphonenumber-for-php/src/libphonenumber/data/PhoneNumberMetadata_SI.php
No syntax errors detected in ./vendor/php-vcr/php-vcr/src/VCR/Event/BeforePlaybackEvent.php
No syntax errors detected in ./vendor/laravel/framework/src/Illuminate/Support/Facades/Blade.php
No syntax errors detected in ./resources/views/emails/appointment/updated/body.blade.php
No syntax errors detected in ./app/WL/Modules/Location/Commands/RemoveClientLocationCommand.php


Yet, when I try to parse one of those files I see that it does produce the expected output (either passing or failing parsing):



$ php -l ./bootstrap/cache/services.php
No syntax errors detected in ./bootstrap/cache/services.php


I've checked that neither passing nor failing linting is printing the expected lines to stderr:



$ php -l good.php | grep rr
No syntax errors detected in good.php

$ php -l bad.php | grep rr
PHP Parse error: syntax error, unexpected ''foo'' (T_CONSTANT_ENCAPSED_STRING), expecting ')' in bad.php on line 3
Errors parsing bad.php


What should I check now? My end goal is to lint all the files, then grep for Error parsing to fix those issues.







bash shell php xargs debugging






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 14 hours ago









dotancohendotancohen

6,423195996




6,423195996







  • 1





    Can the php -l command take multiple arguments with the syntax php -l file1 file2 file3? xargs would be passing the results of find in batches.

    – Haxiel
    14 hours ago











  • @Haxiel: Thank you, in fact xargs was batching. Learn something every day!

    – dotancohen
    14 hours ago












  • 1





    Can the php -l command take multiple arguments with the syntax php -l file1 file2 file3? xargs would be passing the results of find in batches.

    – Haxiel
    14 hours ago











  • @Haxiel: Thank you, in fact xargs was batching. Learn something every day!

    – dotancohen
    14 hours ago







1




1





Can the php -l command take multiple arguments with the syntax php -l file1 file2 file3? xargs would be passing the results of find in batches.

– Haxiel
14 hours ago





Can the php -l command take multiple arguments with the syntax php -l file1 file2 file3? xargs would be passing the results of find in batches.

– Haxiel
14 hours ago













@Haxiel: Thank you, in fact xargs was batching. Learn something every day!

– dotancohen
14 hours ago





@Haxiel: Thank you, in fact xargs was batching. Learn something every day!

– dotancohen
14 hours ago










1 Answer
1






active

oldest

votes


















7














To see whether xargs makes a difference, run the command lines that it runs. Here are a couple of ways to see exactly what it runs, while not risking changing what it runs:



  • Write a script called php in a temporary directory and put it at the beginning of $PATH. In this script, log the arguments (and optionally run the real php afterwards).

  • Run the whole command line under a logging mechanism such as strace.

You will find that the command is something like



php -l ./bootstrap/app.php ./bootstrap/autoload.php ./bootstrap/cache/services.php …


The next step is to investigate what this command does.



I'm not familiar with php but I guess it only treats the first file name as a PHP script name, and that in lint mode it simply ignores all subsequent arguments. So you need to run php -l once for each script, 12147 times in total, instead of using xargs's grouping behavior.



The easiest way to do that is



find . -name *.php -exec php -l ;


but this command will always return 0 even if some invocations of php return a nonzero status. While find mostly doesn't need xargs in the 21st century, a benefit of xargs is that it returns a nonzero status if any invocation of the command returns a nonzero status. So run xargs, but tell it to only process one file at a time with the -n option.



find . -name *.php -print0 | xargs -0 -n 1 php -l





share|improve this answer























  • As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

    – dotancohen
    14 hours ago










Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505880%2fwho-is-eating-data-xargs%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









7














To see whether xargs makes a difference, run the command lines that it runs. Here are a couple of ways to see exactly what it runs, while not risking changing what it runs:



  • Write a script called php in a temporary directory and put it at the beginning of $PATH. In this script, log the arguments (and optionally run the real php afterwards).

  • Run the whole command line under a logging mechanism such as strace.

You will find that the command is something like



php -l ./bootstrap/app.php ./bootstrap/autoload.php ./bootstrap/cache/services.php …


The next step is to investigate what this command does.



I'm not familiar with php but I guess it only treats the first file name as a PHP script name, and that in lint mode it simply ignores all subsequent arguments. So you need to run php -l once for each script, 12147 times in total, instead of using xargs's grouping behavior.



The easiest way to do that is



find . -name *.php -exec php -l ;


but this command will always return 0 even if some invocations of php return a nonzero status. While find mostly doesn't need xargs in the 21st century, a benefit of xargs is that it returns a nonzero status if any invocation of the command returns a nonzero status. So run xargs, but tell it to only process one file at a time with the -n option.



find . -name *.php -print0 | xargs -0 -n 1 php -l





share|improve this answer























  • As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

    – dotancohen
    14 hours ago















7














To see whether xargs makes a difference, run the command lines that it runs. Here are a couple of ways to see exactly what it runs, while not risking changing what it runs:



  • Write a script called php in a temporary directory and put it at the beginning of $PATH. In this script, log the arguments (and optionally run the real php afterwards).

  • Run the whole command line under a logging mechanism such as strace.

You will find that the command is something like



php -l ./bootstrap/app.php ./bootstrap/autoload.php ./bootstrap/cache/services.php …


The next step is to investigate what this command does.



I'm not familiar with php but I guess it only treats the first file name as a PHP script name, and that in lint mode it simply ignores all subsequent arguments. So you need to run php -l once for each script, 12147 times in total, instead of using xargs's grouping behavior.



The easiest way to do that is



find . -name *.php -exec php -l ;


but this command will always return 0 even if some invocations of php return a nonzero status. While find mostly doesn't need xargs in the 21st century, a benefit of xargs is that it returns a nonzero status if any invocation of the command returns a nonzero status. So run xargs, but tell it to only process one file at a time with the -n option.



find . -name *.php -print0 | xargs -0 -n 1 php -l





share|improve this answer























  • As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

    – dotancohen
    14 hours ago













7












7








7







To see whether xargs makes a difference, run the command lines that it runs. Here are a couple of ways to see exactly what it runs, while not risking changing what it runs:



  • Write a script called php in a temporary directory and put it at the beginning of $PATH. In this script, log the arguments (and optionally run the real php afterwards).

  • Run the whole command line under a logging mechanism such as strace.

You will find that the command is something like



php -l ./bootstrap/app.php ./bootstrap/autoload.php ./bootstrap/cache/services.php …


The next step is to investigate what this command does.



I'm not familiar with php but I guess it only treats the first file name as a PHP script name, and that in lint mode it simply ignores all subsequent arguments. So you need to run php -l once for each script, 12147 times in total, instead of using xargs's grouping behavior.



The easiest way to do that is



find . -name *.php -exec php -l ;


but this command will always return 0 even if some invocations of php return a nonzero status. While find mostly doesn't need xargs in the 21st century, a benefit of xargs is that it returns a nonzero status if any invocation of the command returns a nonzero status. So run xargs, but tell it to only process one file at a time with the -n option.



find . -name *.php -print0 | xargs -0 -n 1 php -l





share|improve this answer













To see whether xargs makes a difference, run the command lines that it runs. Here are a couple of ways to see exactly what it runs, while not risking changing what it runs:



  • Write a script called php in a temporary directory and put it at the beginning of $PATH. In this script, log the arguments (and optionally run the real php afterwards).

  • Run the whole command line under a logging mechanism such as strace.

You will find that the command is something like



php -l ./bootstrap/app.php ./bootstrap/autoload.php ./bootstrap/cache/services.php …


The next step is to investigate what this command does.



I'm not familiar with php but I guess it only treats the first file name as a PHP script name, and that in lint mode it simply ignores all subsequent arguments. So you need to run php -l once for each script, 12147 times in total, instead of using xargs's grouping behavior.



The easiest way to do that is



find . -name *.php -exec php -l ;


but this command will always return 0 even if some invocations of php return a nonzero status. While find mostly doesn't need xargs in the 21st century, a benefit of xargs is that it returns a nonzero status if any invocation of the command returns a nonzero status. So run xargs, but tell it to only process one file at a time with the -n option.



find . -name *.php -print0 | xargs -0 -n 1 php -l






share|improve this answer












share|improve this answer



share|improve this answer










answered 14 hours ago









GillesGilles

542k12810961615




542k12810961615












  • As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

    – dotancohen
    14 hours ago

















  • As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

    – dotancohen
    14 hours ago
















As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

– dotancohen
14 hours ago





As usual, you've hit the nail right on the head. xargs was batching the arguments, and the -n 1 flag was the right solution. In fact I was using -exec to continue working while this question was being resolved, but I prefer xargs as I feel it is a more flexible solution. Thank you.

– dotancohen
14 hours ago

















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f505880%2fwho-is-eating-data-xargs%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Can not update quote_id field of “quote_item” table magento 2Magento 2.1 - We can't remove the item. (Shopping Cart doesnt allow us to remove items before becomes empty)Add value for custom quote item attribute using REST apiREST API endpoint v1/carts/cartId/items always returns error messageCorrect way to save entries to databaseHow to remove all associated quote objects of a customer completelyMagento 2 - Save value from custom input field to quote_itemGet quote_item data using quote id and product id filter in Magento 2How to set additional data to quote_item table from controller in Magento 2?What is the purpose of additional_data column in quote_item table in magento2Set Custom Price to Quote item magento2 from controller

Nissan Patrol Зміст Перше покоління — 4W60 (1951-1960) | Друге покоління — 60 series (1960-1980) | Третє покоління (1980–2002) | Четверте покоління — Y60 (1987–1998) | П'яте покоління — Y61 (1997–2013) | Шосте покоління — Y62 (2010- ) | Посилання | Зноски | Навігаційне менюОфіційний український сайтТест-драйв Nissan Patrol 2010 7-го поколінняNissan PatrolКак мы тестировали Nissan Patrol 2016рвиправивши або дописавши її

Перекидне табло Зміст Переваги | Недоліки | Будова | Посилання | Навігаційне менюПерекидне таблоU.S. Patent 3 220 174U.S. Patent 3 501 761Split-flap-display