Priority Increasing
From: Ashwin Chandra (ashcs_at_ucla.edu)
Date: 02/28/05
- Previous message: Maxim Sobolev: "Re: RFC: backporting GEOM to the 4.x branch"
- Next in thread: Coleman Kane: "Re: Priority Increasing"
- Reply: Coleman Kane: "Re: Priority Increasing"
- Maybe reply: Ashwin Chandra: "Fw: Priority Increasing"
- Reply: Mike Silbersack: "Re: Priority Increasing"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: <freebsd-hackers@freebsd.org> Date: Sun, 27 Feb 2005 18:11:57 -0800
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"
- Previous message: Maxim Sobolev: "Re: RFC: backporting GEOM to the 4.x branch"
- Next in thread: Coleman Kane: "Re: Priority Increasing"
- Reply: Coleman Kane: "Re: Priority Increasing"
- Maybe reply: Ashwin Chandra: "Fw: Priority Increasing"
- Reply: Mike Silbersack: "Re: Priority Increasing"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]