system() function string length limit The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) The Ask Question Wizard is Live! Data science time! April 2019 and salary with experienceHow can I get a file's size in C?How do function pointers in C work?How does free know how much to free?Improve INSERT-per-second performance of SQLite?What does “#define _GNU_SOURCE” imply?Maximum length of command line argument that can be passed to SQL*Plus?Why are elementwise additions much faster in separate loops than in a combined loop?POSIX limits the number of character acceptable as user input to 4096, how to increase it?Does Posix supply format string macros for printf/scanf?Define length-prefixed const wide string in C

The following signatures were invalid: EXPKEYSIG 1397BC53640DB551

Does the AirPods case need to be around while listening via an iOS Device?

Didn't get enough time to take a Coding Test - what to do now?

How many people can fit inside Mordenkainen's Magnificent Mansion?

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

Segmentation fault output is suppressed when piping stdin into a function. Why?

ELI5: Why do they say that Israel would have been the fourth country to land a spacecraft on the Moon and why do they call it low cost?

Take groceries in checked luggage

Semisimplicity of the category of coherent sheaves?

Was credit for the black hole image misattributed?

Difference between "generating set" and free product?

Keeping a retro style to sci-fi spaceships?

What aspect of planet Earth must be changed to prevent the industrial revolution?

Why can't wing-mounted spoilers be used to steepen approaches?

Do warforged have souls?

First use of “packing” as in carrying a gun

Is it ethical to upload a automatically generated paper to a non peer-reviewed site as part of a larger research?

How to copy the contents of all files with a certain name into a new file?

Is there a writing software that you can sort scenes like slides in PowerPoint?

Who or what is the being for whom Being is a question for Heidegger?

What are these Gizmos at Izaña Atmospheric Research Center in Spain?

Windows 10: How to Lock (not sleep) laptop on lid close?

Am I ethically obligated to go into work on an off day if the reason is sudden?

I could not break this equation. Please help me



system() function string length limit



The 2019 Stack Overflow Developer Survey Results Are In
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
The Ask Question Wizard is Live!
Data science time! April 2019 and salary with experienceHow can I get a file's size in C?How do function pointers in C work?How does free know how much to free?Improve INSERT-per-second performance of SQLite?What does “#define _GNU_SOURCE” imply?Maximum length of command line argument that can be passed to SQL*Plus?Why are elementwise additions much faster in separate loops than in a combined loop?POSIX limits the number of character acceptable as user input to 4096, how to increase it?Does Posix supply format string macros for printf/scanf?Define length-prefixed const wide string in C



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








8















How long can be a string passed to system()?



I know the POSIX minimum is 4096, but I would like to know the actual size I can use. Is there any macro defined in any header for that, similar to FILENAME_MAX?



char cmd[SOME_MACRO];

...
system(cmd);









share|improve this question



















  • 3





    Start worrying if your string is more than 100 KiB. Until then, you should be OK.

    – Jonathan Leffler
    8 hours ago











  • @JL2210: cannot use that, SIZE_MAX is not the maximum string length, it is the maximum value for type size_t. This value is usually much larger than anything you can define, especially with automatic storage!

    – chqrlie
    8 hours ago











  • @JL2210: same thing, cannot really use that for allocation

    – chqrlie
    8 hours ago











  • OK. But the maximum length defined in the C library is size_t (see return value of strlen).

    – JL2210
    8 hours ago












  • If this is a problem for your programming, you are better off writing the command arguments into a file and updating the command to read that. Many programs, like the compiler and linker on Windows, can already read arguments from a file. Some Unix programs like xargs can read a stream of arguments and run one copy of the command template for each n arguments.

    – Zan Lynx
    19 mins ago

















8















How long can be a string passed to system()?



I know the POSIX minimum is 4096, but I would like to know the actual size I can use. Is there any macro defined in any header for that, similar to FILENAME_MAX?



char cmd[SOME_MACRO];

...
system(cmd);









share|improve this question



















  • 3





    Start worrying if your string is more than 100 KiB. Until then, you should be OK.

    – Jonathan Leffler
    8 hours ago











  • @JL2210: cannot use that, SIZE_MAX is not the maximum string length, it is the maximum value for type size_t. This value is usually much larger than anything you can define, especially with automatic storage!

    – chqrlie
    8 hours ago











  • @JL2210: same thing, cannot really use that for allocation

    – chqrlie
    8 hours ago











  • OK. But the maximum length defined in the C library is size_t (see return value of strlen).

    – JL2210
    8 hours ago












  • If this is a problem for your programming, you are better off writing the command arguments into a file and updating the command to read that. Many programs, like the compiler and linker on Windows, can already read arguments from a file. Some Unix programs like xargs can read a stream of arguments and run one copy of the command template for each n arguments.

    – Zan Lynx
    19 mins ago













8












8








8








How long can be a string passed to system()?



I know the POSIX minimum is 4096, but I would like to know the actual size I can use. Is there any macro defined in any header for that, similar to FILENAME_MAX?



char cmd[SOME_MACRO];

...
system(cmd);









share|improve this question
















How long can be a string passed to system()?



I know the POSIX minimum is 4096, but I would like to know the actual size I can use. Is there any macro defined in any header for that, similar to FILENAME_MAX?



char cmd[SOME_MACRO];

...
system(cmd);






c linux posix






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 16 mins ago









Charles Duffy

181k28206261




181k28206261










asked 8 hours ago









Cacahuete FritoCacahuete Frito

656620




656620







  • 3





    Start worrying if your string is more than 100 KiB. Until then, you should be OK.

    – Jonathan Leffler
    8 hours ago











  • @JL2210: cannot use that, SIZE_MAX is not the maximum string length, it is the maximum value for type size_t. This value is usually much larger than anything you can define, especially with automatic storage!

    – chqrlie
    8 hours ago











  • @JL2210: same thing, cannot really use that for allocation

    – chqrlie
    8 hours ago











  • OK. But the maximum length defined in the C library is size_t (see return value of strlen).

    – JL2210
    8 hours ago












  • If this is a problem for your programming, you are better off writing the command arguments into a file and updating the command to read that. Many programs, like the compiler and linker on Windows, can already read arguments from a file. Some Unix programs like xargs can read a stream of arguments and run one copy of the command template for each n arguments.

    – Zan Lynx
    19 mins ago












  • 3





    Start worrying if your string is more than 100 KiB. Until then, you should be OK.

    – Jonathan Leffler
    8 hours ago











  • @JL2210: cannot use that, SIZE_MAX is not the maximum string length, it is the maximum value for type size_t. This value is usually much larger than anything you can define, especially with automatic storage!

    – chqrlie
    8 hours ago











  • @JL2210: same thing, cannot really use that for allocation

    – chqrlie
    8 hours ago











  • OK. But the maximum length defined in the C library is size_t (see return value of strlen).

    – JL2210
    8 hours ago












  • If this is a problem for your programming, you are better off writing the command arguments into a file and updating the command to read that. Many programs, like the compiler and linker on Windows, can already read arguments from a file. Some Unix programs like xargs can read a stream of arguments and run one copy of the command template for each n arguments.

    – Zan Lynx
    19 mins ago







3




3





Start worrying if your string is more than 100 KiB. Until then, you should be OK.

– Jonathan Leffler
8 hours ago





Start worrying if your string is more than 100 KiB. Until then, you should be OK.

– Jonathan Leffler
8 hours ago













@JL2210: cannot use that, SIZE_MAX is not the maximum string length, it is the maximum value for type size_t. This value is usually much larger than anything you can define, especially with automatic storage!

– chqrlie
8 hours ago





@JL2210: cannot use that, SIZE_MAX is not the maximum string length, it is the maximum value for type size_t. This value is usually much larger than anything you can define, especially with automatic storage!

– chqrlie
8 hours ago













@JL2210: same thing, cannot really use that for allocation

– chqrlie
8 hours ago





@JL2210: same thing, cannot really use that for allocation

– chqrlie
8 hours ago













OK. But the maximum length defined in the C library is size_t (see return value of strlen).

– JL2210
8 hours ago






OK. But the maximum length defined in the C library is size_t (see return value of strlen).

– JL2210
8 hours ago














If this is a problem for your programming, you are better off writing the command arguments into a file and updating the command to read that. Many programs, like the compiler and linker on Windows, can already read arguments from a file. Some Unix programs like xargs can read a stream of arguments and run one copy of the command template for each n arguments.

– Zan Lynx
19 mins ago





If this is a problem for your programming, you are better off writing the command arguments into a file and updating the command to read that. Many programs, like the compiler and linker on Windows, can already read arguments from a file. Some Unix programs like xargs can read a stream of arguments and run one copy of the command template for each n arguments.

– Zan Lynx
19 mins ago












3 Answers
3






active

oldest

votes


















8














system exec's a shell with arguments "sh","-c", YourAgumentToSystem, (char*)0 (guaranteed by POSIX), so
the maximum length (not counting the '' terminator) is ARG_MAX -1 -3 -3 - size_of_your_environment.



ARG_MAX is defined in limits.h as




"Maximum length of argument to the exec functions including
environment data."




To measure the size of your environment, you can run:



extern char **environ;
size_t envsz = 0; for(char **e=environ; *e; e++) envsz += strlen(*e)+1;





share|improve this answer




















  • 1





    Note that this value may be large for allocation with automatic storage.

    – chqrlie
    7 hours ago






  • 1





    Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

    – Chris Dodd
    6 hours ago











  • I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

    – Zan Lynx
    17 mins ago


















4














The limit is highly system dependent. It may even depend on the command shell that will be used. You should test the return value of system() to see if the system call was successful: -1 means failure and errno should give you more information. The behavior should be defined for any proper C string.



POSIX documents that system(command) is equivalent to:



execl(<shell path>, "sh", "-c", command, (char *)0);


And also documents ARG_MAX defined in <limits.h> as the limit for the combined lengths of the arguments to exec and the environment variables.



Note however that command may contain wildcards and/or other shell words whose expansion may exceed some other limit. Always check the return value for failure.






share|improve this answer




















  • 1





    @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

    – chqrlie
    8 hours ago






  • 3





    @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

    – chqrlie
    7 hours ago


















3















man 3 system




gives us




DESCRIPTION



The system() library function uses fork(2) to create a child process that executes the shell command specified in command
using execl(3) as follows:



 execl("/bin/sh", "sh", "-c", command, (char *) 0);

system() returns after the command has been completed.


so system() is a wrapper for execl()




From the same page we also see that this call conforms to some standards.




CONFORMING TO



POSIX.1-2001, POSIX.1-2008, C89, C99.




Looking up POSIX.1-2008 produces the following online reference



https://pubs.opengroup.org/onlinepubs/9699919799/



Where we can search for info on the execl function which system takes us to



https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html



Which offers up the following




The number of bytes available for the new process' combined argument and environment lists is ARG_MAX. It is implementation-defined whether null terminators, pointers, and/or any alignment bytes are included in this total.




And finally ...




ERRORS



The exec functions shall fail if:



[E2BIG] The number of bytes used by the new process image's argument
list and environment list is greater than the system-imposed limit of
ARG_MAX bytes.




So the final check to carry out here is the actual exec implementation rather than relying on the standard just in case the implementation deviated from the standard.



So, man 3 execl reports that the errors returned are the same as documented for execve(2) and man 2 execvw reports the following:




ERRORS



E2BIG The total number of bytes in the environment (envp) and argument list (argv) is too large.




Not as precise as the POSIX standard? Best check the code or see the (now) accepted answer :)






share|improve this answer

























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    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: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    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%2fstackoverflow.com%2fquestions%2f55666911%2fsystem-function-string-length-limit%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    8














    system exec's a shell with arguments "sh","-c", YourAgumentToSystem, (char*)0 (guaranteed by POSIX), so
    the maximum length (not counting the '' terminator) is ARG_MAX -1 -3 -3 - size_of_your_environment.



    ARG_MAX is defined in limits.h as




    "Maximum length of argument to the exec functions including
    environment data."




    To measure the size of your environment, you can run:



    extern char **environ;
    size_t envsz = 0; for(char **e=environ; *e; e++) envsz += strlen(*e)+1;





    share|improve this answer




















    • 1





      Note that this value may be large for allocation with automatic storage.

      – chqrlie
      7 hours ago






    • 1





      Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

      – Chris Dodd
      6 hours ago











    • I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

      – Zan Lynx
      17 mins ago















    8














    system exec's a shell with arguments "sh","-c", YourAgumentToSystem, (char*)0 (guaranteed by POSIX), so
    the maximum length (not counting the '' terminator) is ARG_MAX -1 -3 -3 - size_of_your_environment.



    ARG_MAX is defined in limits.h as




    "Maximum length of argument to the exec functions including
    environment data."




    To measure the size of your environment, you can run:



    extern char **environ;
    size_t envsz = 0; for(char **e=environ; *e; e++) envsz += strlen(*e)+1;





    share|improve this answer




















    • 1





      Note that this value may be large for allocation with automatic storage.

      – chqrlie
      7 hours ago






    • 1





      Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

      – Chris Dodd
      6 hours ago











    • I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

      – Zan Lynx
      17 mins ago













    8












    8








    8







    system exec's a shell with arguments "sh","-c", YourAgumentToSystem, (char*)0 (guaranteed by POSIX), so
    the maximum length (not counting the '' terminator) is ARG_MAX -1 -3 -3 - size_of_your_environment.



    ARG_MAX is defined in limits.h as




    "Maximum length of argument to the exec functions including
    environment data."




    To measure the size of your environment, you can run:



    extern char **environ;
    size_t envsz = 0; for(char **e=environ; *e; e++) envsz += strlen(*e)+1;





    share|improve this answer















    system exec's a shell with arguments "sh","-c", YourAgumentToSystem, (char*)0 (guaranteed by POSIX), so
    the maximum length (not counting the '' terminator) is ARG_MAX -1 -3 -3 - size_of_your_environment.



    ARG_MAX is defined in limits.h as




    "Maximum length of argument to the exec functions including
    environment data."




    To measure the size of your environment, you can run:



    extern char **environ;
    size_t envsz = 0; for(char **e=environ; *e; e++) envsz += strlen(*e)+1;






    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 7 hours ago

























    answered 8 hours ago









    PSkocikPSkocik

    35.4k65579




    35.4k65579







    • 1





      Note that this value may be large for allocation with automatic storage.

      – chqrlie
      7 hours ago






    • 1





      Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

      – Chris Dodd
      6 hours ago











    • I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

      – Zan Lynx
      17 mins ago












    • 1





      Note that this value may be large for allocation with automatic storage.

      – chqrlie
      7 hours ago






    • 1





      Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

      – Chris Dodd
      6 hours ago











    • I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

      – Zan Lynx
      17 mins ago







    1




    1





    Note that this value may be large for allocation with automatic storage.

    – chqrlie
    7 hours ago





    Note that this value may be large for allocation with automatic storage.

    – chqrlie
    7 hours ago




    1




    1





    Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

    – Chris Dodd
    6 hours ago





    Its also not guarenteed that exceeding it will fail -- its (just) undefined behavior, so it may work one time you call it and fail the next.

    – Chris Dodd
    6 hours ago













    I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

    – Zan Lynx
    17 mins ago





    I don't think that's the most efficient way to calculate environment size. I believe you can run the pointers up until the NULL and subtract from environ, without involving strlen calls.

    – Zan Lynx
    17 mins ago













    4














    The limit is highly system dependent. It may even depend on the command shell that will be used. You should test the return value of system() to see if the system call was successful: -1 means failure and errno should give you more information. The behavior should be defined for any proper C string.



    POSIX documents that system(command) is equivalent to:



    execl(<shell path>, "sh", "-c", command, (char *)0);


    And also documents ARG_MAX defined in <limits.h> as the limit for the combined lengths of the arguments to exec and the environment variables.



    Note however that command may contain wildcards and/or other shell words whose expansion may exceed some other limit. Always check the return value for failure.






    share|improve this answer




















    • 1





      @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

      – chqrlie
      8 hours ago






    • 3





      @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

      – chqrlie
      7 hours ago















    4














    The limit is highly system dependent. It may even depend on the command shell that will be used. You should test the return value of system() to see if the system call was successful: -1 means failure and errno should give you more information. The behavior should be defined for any proper C string.



    POSIX documents that system(command) is equivalent to:



    execl(<shell path>, "sh", "-c", command, (char *)0);


    And also documents ARG_MAX defined in <limits.h> as the limit for the combined lengths of the arguments to exec and the environment variables.



    Note however that command may contain wildcards and/or other shell words whose expansion may exceed some other limit. Always check the return value for failure.






    share|improve this answer




















    • 1





      @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

      – chqrlie
      8 hours ago






    • 3





      @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

      – chqrlie
      7 hours ago













    4












    4








    4







    The limit is highly system dependent. It may even depend on the command shell that will be used. You should test the return value of system() to see if the system call was successful: -1 means failure and errno should give you more information. The behavior should be defined for any proper C string.



    POSIX documents that system(command) is equivalent to:



    execl(<shell path>, "sh", "-c", command, (char *)0);


    And also documents ARG_MAX defined in <limits.h> as the limit for the combined lengths of the arguments to exec and the environment variables.



    Note however that command may contain wildcards and/or other shell words whose expansion may exceed some other limit. Always check the return value for failure.






    share|improve this answer















    The limit is highly system dependent. It may even depend on the command shell that will be used. You should test the return value of system() to see if the system call was successful: -1 means failure and errno should give you more information. The behavior should be defined for any proper C string.



    POSIX documents that system(command) is equivalent to:



    execl(<shell path>, "sh", "-c", command, (char *)0);


    And also documents ARG_MAX defined in <limits.h> as the limit for the combined lengths of the arguments to exec and the environment variables.



    Note however that command may contain wildcards and/or other shell words whose expansion may exceed some other limit. Always check the return value for failure.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 7 hours ago

























    answered 8 hours ago









    chqrliechqrlie

    63.7k851108




    63.7k851108







    • 1





      @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

      – chqrlie
      8 hours ago






    • 3





      @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

      – chqrlie
      7 hours ago












    • 1





      @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

      – chqrlie
      8 hours ago






    • 3





      @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

      – chqrlie
      7 hours ago







    1




    1





    @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

    – chqrlie
    8 hours ago





    @CacahueteFrito: not that I know. also bear in mind not to allocate too much data with automatic storage. 2MB is already in the risky zone.

    – chqrlie
    8 hours ago




    3




    3





    @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

    – chqrlie
    7 hours ago





    @CacahueteFrito: I was wrong, there is a documented limit: ARG_MAX defined in <limits.h>.

    – chqrlie
    7 hours ago











    3















    man 3 system




    gives us




    DESCRIPTION



    The system() library function uses fork(2) to create a child process that executes the shell command specified in command
    using execl(3) as follows:



     execl("/bin/sh", "sh", "-c", command, (char *) 0);

    system() returns after the command has been completed.


    so system() is a wrapper for execl()




    From the same page we also see that this call conforms to some standards.




    CONFORMING TO



    POSIX.1-2001, POSIX.1-2008, C89, C99.




    Looking up POSIX.1-2008 produces the following online reference



    https://pubs.opengroup.org/onlinepubs/9699919799/



    Where we can search for info on the execl function which system takes us to



    https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html



    Which offers up the following




    The number of bytes available for the new process' combined argument and environment lists is ARG_MAX. It is implementation-defined whether null terminators, pointers, and/or any alignment bytes are included in this total.




    And finally ...




    ERRORS



    The exec functions shall fail if:



    [E2BIG] The number of bytes used by the new process image's argument
    list and environment list is greater than the system-imposed limit of
    ARG_MAX bytes.




    So the final check to carry out here is the actual exec implementation rather than relying on the standard just in case the implementation deviated from the standard.



    So, man 3 execl reports that the errors returned are the same as documented for execve(2) and man 2 execvw reports the following:




    ERRORS



    E2BIG The total number of bytes in the environment (envp) and argument list (argv) is too large.




    Not as precise as the POSIX standard? Best check the code or see the (now) accepted answer :)






    share|improve this answer





























      3















      man 3 system




      gives us




      DESCRIPTION



      The system() library function uses fork(2) to create a child process that executes the shell command specified in command
      using execl(3) as follows:



       execl("/bin/sh", "sh", "-c", command, (char *) 0);

      system() returns after the command has been completed.


      so system() is a wrapper for execl()




      From the same page we also see that this call conforms to some standards.




      CONFORMING TO



      POSIX.1-2001, POSIX.1-2008, C89, C99.




      Looking up POSIX.1-2008 produces the following online reference



      https://pubs.opengroup.org/onlinepubs/9699919799/



      Where we can search for info on the execl function which system takes us to



      https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html



      Which offers up the following




      The number of bytes available for the new process' combined argument and environment lists is ARG_MAX. It is implementation-defined whether null terminators, pointers, and/or any alignment bytes are included in this total.




      And finally ...




      ERRORS



      The exec functions shall fail if:



      [E2BIG] The number of bytes used by the new process image's argument
      list and environment list is greater than the system-imposed limit of
      ARG_MAX bytes.




      So the final check to carry out here is the actual exec implementation rather than relying on the standard just in case the implementation deviated from the standard.



      So, man 3 execl reports that the errors returned are the same as documented for execve(2) and man 2 execvw reports the following:




      ERRORS



      E2BIG The total number of bytes in the environment (envp) and argument list (argv) is too large.




      Not as precise as the POSIX standard? Best check the code or see the (now) accepted answer :)






      share|improve this answer



























        3












        3








        3








        man 3 system




        gives us




        DESCRIPTION



        The system() library function uses fork(2) to create a child process that executes the shell command specified in command
        using execl(3) as follows:



         execl("/bin/sh", "sh", "-c", command, (char *) 0);

        system() returns after the command has been completed.


        so system() is a wrapper for execl()




        From the same page we also see that this call conforms to some standards.




        CONFORMING TO



        POSIX.1-2001, POSIX.1-2008, C89, C99.




        Looking up POSIX.1-2008 produces the following online reference



        https://pubs.opengroup.org/onlinepubs/9699919799/



        Where we can search for info on the execl function which system takes us to



        https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html



        Which offers up the following




        The number of bytes available for the new process' combined argument and environment lists is ARG_MAX. It is implementation-defined whether null terminators, pointers, and/or any alignment bytes are included in this total.




        And finally ...




        ERRORS



        The exec functions shall fail if:



        [E2BIG] The number of bytes used by the new process image's argument
        list and environment list is greater than the system-imposed limit of
        ARG_MAX bytes.




        So the final check to carry out here is the actual exec implementation rather than relying on the standard just in case the implementation deviated from the standard.



        So, man 3 execl reports that the errors returned are the same as documented for execve(2) and man 2 execvw reports the following:




        ERRORS



        E2BIG The total number of bytes in the environment (envp) and argument list (argv) is too large.




        Not as precise as the POSIX standard? Best check the code or see the (now) accepted answer :)






        share|improve this answer
















        man 3 system




        gives us




        DESCRIPTION



        The system() library function uses fork(2) to create a child process that executes the shell command specified in command
        using execl(3) as follows:



         execl("/bin/sh", "sh", "-c", command, (char *) 0);

        system() returns after the command has been completed.


        so system() is a wrapper for execl()




        From the same page we also see that this call conforms to some standards.




        CONFORMING TO



        POSIX.1-2001, POSIX.1-2008, C89, C99.




        Looking up POSIX.1-2008 produces the following online reference



        https://pubs.opengroup.org/onlinepubs/9699919799/



        Where we can search for info on the execl function which system takes us to



        https://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html



        Which offers up the following




        The number of bytes available for the new process' combined argument and environment lists is ARG_MAX. It is implementation-defined whether null terminators, pointers, and/or any alignment bytes are included in this total.




        And finally ...




        ERRORS



        The exec functions shall fail if:



        [E2BIG] The number of bytes used by the new process image's argument
        list and environment list is greater than the system-imposed limit of
        ARG_MAX bytes.




        So the final check to carry out here is the actual exec implementation rather than relying on the standard just in case the implementation deviated from the standard.



        So, man 3 execl reports that the errors returned are the same as documented for execve(2) and man 2 execvw reports the following:




        ERRORS



        E2BIG The total number of bytes in the environment (envp) and argument list (argv) is too large.




        Not as precise as the POSIX standard? Best check the code or see the (now) accepted answer :)







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 7 hours ago

























        answered 7 hours ago









        Rob KieltyRob Kielty

        6,43153047




        6,43153047



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • 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%2fstackoverflow.com%2fquestions%2f55666911%2fsystem-function-string-length-limit%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

            Dapidodigma demeter Subspecies | Notae | Tabula navigationisDapidodigmaAfrotropical Butterflies: Lycaenidae - Subtribe IolainaAmplifica

            Constantinus Vanšenkin Nexus externi | Tabula navigationisБольшая российская энциклопедияAmplifica

            Gaius Norbanus Flaccus (consul 38 a.C.n.) Index De gente | De cursu honorum | Notae | Fontes | Si vis plura legere | Tabula navigationisHic legere potes