Closed GoogleCodeExporter closed 9 years ago
Hi, it's a simple and ugly hack but as I've only two cores and I that would
like to
keep one of them free to keep my system responsive I've modified util.py in
cpyrit
directory of the 0.2.4 src tarball.
At line 65 (because I'm using linux of course!) change "return nbcpus" to
"return
nbcpus -1" then redo the install process.
I'm not sure about it but doing this on a single core cpu could break
everything...
You have been warned, this is just a little hack :-P
Original comment by dory.thi...@gmail.com
on 28 Dec 2009 at 1:41
it is SO obvious that I never think to this solution. At my eyes it is simply
and
elegant at same time, not ugly. Anyway, better to add a control to avoid to do
decrement nbcpus case of monocore CPU :-) something as this (really ugly)
pseudo code :
if nbcpus = 1 then return nbcpus
if leave_one_core_free <> 1 AND nbcpus > 1 then return nbcpus
if leave_one_core_free = 1 AND nbcpus > 1 then return nbcpus - 1
Original comment by pyrit.lo...@gmail.com
on 28 Dec 2009 at 8:26
I would prefer some pyrit command that gives you choice from cores. (which
cores do
you want to use)
Original comment by bi...@seznam.cz
on 5 Jan 2010 at 12:40
The number of used CPUs can now be limited by the option 'limit_ncpus' in
Pyrit's configuration file. For example, add this to ~/.pyrit/config
limit_ncpus = 1
Original comment by lukas.l...@gmail.com
on 23 Jul 2010 at 4:20
Great feature, but doesn't seem to work on a CoreDuo, Ubuntu 10.04. I've tried
setting to 0, 1 and 2, but to no effect.
Original comment by dkaloya...@gmail.com
on 28 Jul 2010 at 11:15
Here's what I get:
WARNING: Unknown option 'limit_ncpus' in configfile '/root/.pyrit/config'
Pyrit 0.3.0 (C) 2008-2010 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+
Original comment by dkaloya...@gmail.com
on 28 Jul 2010 at 11:19
You're on 0.3.0. The option limit_ncpus is available from 0.3.1-svn r275
onwards or in Debian's version of 0.3.0
Original comment by lukas.l...@gmail.com
on 28 Jul 2010 at 11:52
I see, thank you and sorry to bother you. Keep up the excellent work on this
software!
Original comment by dkaloya...@gmail.com
on 29 Jul 2010 at 6:57
Nice to know anoter option is avaiable.
but why parameter must be placed into config file and cannot be forced as
command line parameter?
I supposed pyrit should accept all parameters in command line, can I ask why
you decided to move it inside config file?
Better, both possibility should be accepted: in config file should stay
default parameters (i.e: limit_ncpus = use_all) and in command line should be
possible to decide a different beaviour (i.e. pyrit -limit_cpus=1 etc etc)
My 2 cents
Original comment by pyrit.lo...@gmail.com
on 29 Jul 2010 at 1:48
Original issue reported on code.google.com by
pyrit.lo...@gmail.com
on 21 Nov 2009 at 12:49