commit | 5799e9cd37301ab74436954e860250c3f26e4d79 | [log] [tgz] |
---|---|---|
author | Willy Tarreau <w@1wt.eu> | Tue Mar 05 18:14:03 2019 +0100 |
committer | Willy Tarreau <w@1wt.eu> | Tue Mar 05 18:14:03 2019 +0100 |
tree | 3db6f5f1ce65f7e276cbedb5f9d893c625c82ea6 | |
parent | 8e5e1e7bf000f2603a085c76be118214d22c55b4 [diff] |
MINOR: config: relax the range checks on cpu-map Emeric reports that when MAX_THREADS and/or MAX_PROCS are set to lower values, referencing thread or process numbers higher than these limits in cpu-map returns errors. This is annoying because these typically are silent settings that are expected to be used only when set. Let's switch back to LONGBITS for this limit.