3 idle class takes no priority. thanks @gardenhead
source | link

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 -n7 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...
    

Once set up, neither approach requires root access. Moreover you can decide in advance which jobs should be subject to this control, and which must not.

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 -n7 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...
    

Once set up, neither approach requires root access. Moreover you can decide in advance which jobs should be subject to this control, and which must not.

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...
    

Once set up, neither approach requires root access. Moreover you can decide in advance which jobs should be subject to this control, and which must not.

2 added 152 characters in body
source | link

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 -n7 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...
    

Once set up, neither approach requires root access. Moreover you can decide in advance which jobs should be subject to this control, and which must not.

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 -n7 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...
    

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 -n7 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...
    

Once set up, neither approach requires root access. Moreover you can decide in advance which jobs should be subject to this control, and which must not.

1
source | link

I would consider two approaches

  1. Leave the scheduling untouched but run all cron jobs under nice, and possibly even ionice:

    0 * * * *    root    ionice -c3 -n7 nice /some/command and parameters
    
  2. Disallow any cron jobs during certain times. Remember that any user who can create (or remove) the flag file can control this approach. That might work if you want to have a gaming mode that is set up on demand, by adding the touch and rm commands to your game's start-up script. (You might need to use /tmp rather than /var/run, but then it's trivially open to any user.)

    0 18 * * *      root    touch /var/run/no_cron
    0 19 * * *      root    rm -f /var/run/no_cron
    
    0 * * * *       root    test ! -f /var/run/no_cron && /some/command...