Re: Priority Increasing

From: Coleman Kane (zombyfork_at_gmail.com)
Date: 02/28/05

  • Next message: Ashwin Chandra: "Fw: Priority Increasing"
    Date: Sun, 27 Feb 2005 22:28:23 -0500
    To: Ashwin Chandra <ashcs@ucla.edu>
    
    

    Well, since the program is running a forkbomb, it is gonna stress out
    the kernel. The kernel is constantly creating new process spaces, as
    well as filling in the queue.

    Are we talking a O(2^n) forkbomb here (where the forks also fork)?
    Remember, there is overhead associated with forking off new processes,
    and if your program is doing it continuously, nicing them is not going
    to fix the problem. I suggest you fix the program so that it doesn't
    forkbomb.

    You can also rlimit it, and force the number of processes to a
    specific ceiling. This will result in crashing the program everytime
    you hit that limit, however. Try looking into djb's daemontools if you
    want to duct-tape it (ports/sysutils/daemontools)

    --
    coleman
    On Sun, 27 Feb 2005 18:11:57 -0800, Ashwin Chandra <ashcs@ucla.edu> wrote:
    > Hi all,
    > Ive been trying to counter the malicious effects of a forkbomb by setting the forkbomb parent and children to a PRI_MAX priority, although this is not having any effect on the system load.
    > 
    > Basically in my code when I know which process is acting maliciously (forkbomb), I run the following simple code:
    > 
    >       FOREACH_KSEGRP_IN_PROC(p, kg)
    >         {
    >           printf("old prio:%d", kg->kg_user_pri);
    >           kg->kg_user_pri = PRI_MAX;
    >           printf(" new prio:%d", kg->kg_user_pri);
    >         }
    > 
    > When it prints out, the old prio was 180 and the new gets set to 255 although there is help to the system...the system is still under stress. Do you guys know any good ways of hacking the scheduler to make a process that is bad run MUCH MUCH less as to not overload the system?
    > 
    > Ash
    > _______________________________________________
    > freebsd-hackers@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    >
    _______________________________________________
    freebsd-hackers@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
    To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
    

  • Next message: Ashwin Chandra: "Fw: Priority Increasing"

    Relevant Pages

    • Re: forkbombing Linux distributions
      ... > from grabbing so much memory that your computer enters swap death, ... I find that this forkbomb doesnt always kill the machine. ... process will be killed after a while (by the kernel) ...
      (Linux-Kernel)
    • Priority Increasing
      ... Ive been trying to counter the malicious effects of a forkbomb by setting the forkbomb parent and children to a PRI_MAX priority, although this is not having any effect on the system load. ...
      (freebsd-hackers)
    • Re: forkbombing Linux distributions
      ... > the above forkbomb will stop quickly ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in ... More majordomo info at http://vger.kernel.org/majordomo-info.html ... Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)