[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FE87D92.7060109@banquise.net>
Date: Mon, 25 Jun 2012 17:02:42 +0200
From: Simon Marechal <simon@...quise.net>
To: john-dev@...ts.openwall.com
Subject: Re: Markov: allow start and/or end to be specified in
percent
On 25/06/2012 17:00, Simon Marechal wrote:
> On 25/06/2012 15:41, Frank Dittrich wrote:
>> Thinking further, this would be unnecessary if --node=MIN[-MAX]/COUNT
>> would be supported.
>> I think that code is currently not even in bleeding.
>> But was the code that broken that it wouldn't be a good addition for
>> next jumbo?
>> I know that --fork had problems, but --node?
>
> Node would be the preferred solution I believe.
Or both actually ... -markov:x:30%:55%:x -node 4-6/18 should cut the 25%
between 30% and 55% in 18 chunks and allocate 4-6 to this node. This is
probably overkill, but will be less confusing than having your previous
markov command lines parameters ignored because -node is specified.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
