{
    "content": [
        {
            "type": "text",
            "text": "# nice (info)\n\n## Sections\n\n- **File: coreutils.info,  Node: nice invocation,  Next: nohup invocation,  Prev: env invocation,  Up: Modified command invocation** (1 subsections)\n- **Otherwise, 'nice' runs the given COMMAND with its niceness adjusted.  By**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "nice",
        "section": "",
        "mode": "info",
        "summary": null,
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "File: coreutils.info,  Node: nice invocation,  Next: nohup invocation,  Prev: env invocation,  Up: Modified command invocation",
                "lines": 1,
                "subsections": [
                    {
                        "name": "23.3 'nice': Run a command with modified niceness",
                        "lines": 7
                    }
                ]
            },
            {
                "name": "Otherwise, 'nice' runs the given COMMAND with its niceness adjusted.  By",
                "lines": 95,
                "subsections": []
            }
        ],
        "sections": {
            "File: coreutils.info,  Node: nice invocation,  Next: nohup invocation,  Prev: env invocation,  Up: Modified command invocation": {
                "content": "",
                "subsections": [
                    {
                        "name": "23.3 'nice': Run a command with modified niceness",
                        "content": "'nice' prints a process's \"niceness\", or runs a command with modified\nniceness.  \"niceness\" affects how favorably the process is scheduled in\nthe system.  Synopsis:\n\nnice [OPTION]... [COMMAND [ARG]...]\n\nIf no arguments are given, 'nice' prints the current niceness."
                    }
                ]
            },
            "Otherwise, 'nice' runs the given COMMAND with its niceness adjusted.  By": {
                "content": "default, its niceness is incremented by 10.\n\nNiceness values range at least from -20 (process has high priority\nand gets more resources, thus slowing down other processes) through 19\n(process has lower priority and runs slowly itself, but has less impact\non the speed of other running processes).  Some systems may have a wider\nrange of niceness values; conversely, other systems may enforce more\nrestrictive limits.  An attempt to set the niceness outside the\nsupported range is treated as an attempt to use the minimum or maximum\nsupported value.\n\nA niceness should not be confused with a scheduling priority, which\nlets applications determine the order in which threads are scheduled to\nrun.  Unlike a priority, a niceness is merely advice to the scheduler,\nwhich the scheduler is free to ignore.  Also, as a point of terminology,\nPOSIX defines the behavior of 'nice' in terms of a \"nice value\", which\nis the non-negative difference between a niceness and the minimum\nniceness.  Though 'nice' conforms to POSIX, its documentation and\ndiagnostics use the term \"niceness\" for compatibility with historical\npractice.\n\nCOMMAND must not be a special built-in utility (*note Special\nbuilt-in utilities::).\n\nDue to shell aliases and built-in 'nice' functions, using an\nunadorned 'nice' interactively or in a script may get you different\nfunctionality than that described here.  Invoke it via 'env' (i.e., 'env\nnice ...') to avoid interference from the shell.\n\nNote to change the \"niceness\" of an existing process, one needs to\nuse the 'renice' command.\n\nThe program accepts the following option.  Also see *note Common\noptions::.  Options must precede operands.\n\n'-n ADJUSTMENT'\n'--adjustment=ADJUSTMENT'\nAdd ADJUSTMENT instead of 10 to the command's niceness.  If\nADJUSTMENT is negative and you lack appropriate privileges, 'nice'\nissues a warning but otherwise acts as if you specified a zero\nadjustment.\n\nFor compatibility 'nice' also supports an obsolete option syntax\n'-ADJUSTMENT'.  New scripts should use '-n ADJUSTMENT' instead.\n\n'nice' is installed only on systems that have the POSIX 'setpriority'\nfunction, so portable scripts should not rely on its existence on\nnon-POSIX platforms.\n\nExit status:\n\n0   if no COMMAND is specified and the niceness is output\n125 if 'nice' itself fails\n126 if COMMAND is found but cannot be invoked\n127 if COMMAND cannot be found\nthe exit status of COMMAND otherwise\n\nIt is sometimes useful to run a non-interactive program with reduced\nniceness.\n\n$ nice factor 4611686018427387903\n\nSince 'nice' prints the current niceness, you can invoke it through\nitself to demonstrate how it works.\n\nThe default behavior is to increase the niceness by '10':\n\n$ nice\n0\n$ nice nice\n10\n$ nice -n 10 nice\n10\n\nThe ADJUSTMENT is relative to the current niceness.  In the next\nexample, the first 'nice' invocation runs the second one with niceness\n10, and it in turn runs the final one with a niceness that is 3 more:\n\n$ nice nice -n 3 nice\n13\n\nSpecifying a niceness larger than the supported range is the same as\nspecifying the maximum supported value:\n\n$ nice -n 10000000000 nice\n19\n\nOnly a privileged user may run a process with lower niceness:\n\n$ nice -n -1 nice\nnice: cannot set niceness: Permission denied\n0\n$ sudo nice -n -1 nice\n-1\n",
                "subsections": []
            }
        }
    }
}