distributed cracking: relation between -s/-l value and Restore.Point value when cracked

[ytbe.use3]

There's no problem dividing the keyspace unevenly. In fact, I wouldn't even do it that way. It's just a nice way to explain the system to new users. For advanced -l calculation you'd use --progress-only to find out the ideal -l size.

Sounds good. I will look more into that flag. Do you have some links / resources where this is demonstrated with examples?