HPCC-9551 Allow Roxie to set thread priorities

Previous fix here was not sufficient

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
Merge pull request #5458 from richardkchapman/roxie-threadpriorities

HPCC-9551 Allow Roxie to set thread priorities

Reviewed-by: Gavin Halliday <ghalliday@hpccsystems.com>
HPCC-8430 Document addScopes utility in LDAP section

Signed-off-by: JamesDeFabia <James.Defabia@LexisNexis.com>
Merge pull request #5474 from JamesDeFabia/8430_DocumentAddscopesTool

HPCC-8430 Document addScopes utility in LDAP section

Reviewed-By: Russ Whitehead <william.whitehead@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
HPCC-10895 Document "allow-foreign" option in CLI

Signed-off-by: JamesDeFabia <James.Defabia@LexisNexis.com>
HPCC-10895 Edits from review feedback

Signed-off-by: JamesDeFabia <James.Defabia@LexisNexis.com>
Merge pull request #5478 from JamesDeFabia/10895_document_CLI_Options_ForeignFiles

HPCC-10895 Document "allow-foreign" option in CLI

Reviewed-By: Anthony Fishbeck <anthony.fishbeck@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
Community Edition 4.2.2-1 Gold

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
HPCC-10978 Fix windows build break by removing use of strncasecmp

Signed-off-by: Anthony Fishbeck <anthony.fishbeck@lexisnexis.com>
Merge pull request #5497 from afishbeck/windowsStrncasecmp

HPCC-10978 Fix windows build breack by removing use of strncasecmp

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
HPCC-10698 - Avoid deadlock if retrying lock on superfiles

Two problems:
1) A change introduced in this commit:
19beb0cee074faf6fbde55233507eba897c6d41a

.. caused attempt to lock a file for a transaction, to unlock
the file (completely) pause and retry, this had the nasty side
effect if the file in question was a superfile, of unlocking
the super only, leaving all the sub files locked.
As a consequence competing transactions would have still
locked each other out.

2) A implict transaction (a super operation without a
start/finish super transaction call), used the same transaction
mechanism. If it failed to lock and retried, it cleared it's
locks and cache of files and paused to retry. On the next
attempt it would look the files up again and relock.
Unfortunately, in an implicit super operation, the caller is
the super file the op. is being performed on and as a
consequence, it is never released, but because the cache was,
the retry mechansim looked up the file again and gained a
2nd lock to the super (and all it's subfiles). As a result,
it would deadlock itself.

This fix:
+  removes the unlock(completely)/pause mechanism on
individual files, introduced by:
19beb0cee074faf6fbde55233507eba897c6d41a
+ Checks if file locked without any timeout, i.e. if locked
stop trying (transaction mechanism pauses retries itself)
This avoids wasteful blocking time, when transaction has
locks to some, whilst blocking waiting on others.
+ Ensures the superfile involved in implicit transactions,
remains in the file cache, so that on retry it is reused and
not looked up again causing deadlock.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>