From 011c8315844ae73afaaa2dcf682ce7aa4981eb46 Mon Sep 17 00:00:00 2001 From: Krzysztof Nozderko Date: Mon, 26 Feb 2024 12:22:27 +0100 Subject: [PATCH] SNOW-990111 Update easy logging documentation (#875) ### Description SNOW-990111 Update easy logging documentation ### Checklist - [x] Code compiles correctly - [x] Code is formatted according to [Coding Conventions](../CodingConventions.md) - [x] Created tests which fail without the change (if possible) - [x] All tests passing (`dotnet test`) - [x] Extended the README / documentation, if necessary - [x] Provide JIRA issue id (if possible) or GitHub issue id in PR name --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a719edbcc..c65b3d76b 100644 --- a/README.md +++ b/README.md @@ -793,7 +793,6 @@ The feature is activated by a config file which can be: 2. provided as environmental variable called `SF_CLIENT_CONFIG_FILE` (eg. `SET SF_CLIENT_CONFIG_FILE=C:\some-path\client_config.json`) 3. found in the driver location by searching for `sf_client_config.json` file 4. found in the home location by searching for `sf_client_config.json` file -5. found in temp directory location by searching for `sf_client_config.json` file The search for a config file is executed in the order listed above. @@ -801,6 +800,8 @@ To minimize the number of searches for a configuration file it is executed only: - for the first connection - for the first connection with `CLIENT_CONFIG_FILE` parameter. +On Unix-style systems, client configuration file permissions are expected to have a limitation that only the file owner can modify the files (e.g. 600, 644). + The example of the configuration file is: ```json {