From fc04d8b20cc11c5c5afd82a9c226acc146808a12 Mon Sep 17 00:00:00 2001 From: Stevan Date: Sat, 8 Feb 2025 22:37:36 +0000 Subject: [PATCH] change PRIMEDB to SokweDB --- doc/src/architecture/users.m4 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/src/architecture/users.m4 b/doc/src/architecture/users.m4 index ae41e4c..7ec749a 100644 --- a/doc/src/architecture/users.m4 +++ b/doc/src/architecture/users.m4 @@ -70,7 +70,7 @@ Those people with administrator privileges will typically have 2 logins, one ordinary login and a second login with administrator privileges. The administrative login should be used only when necessary, as when a -new person is given access to PRIMEDB and a new database login must be +new person is given access to SokweDB and a new database login must be created. Ordinary interactions with the database, data entry, data retrieval, etc., should be done with a non-administrator login. @@ -93,10 +93,10 @@ PostgreSQL superuser. a PostgreSQL_ role that can login and create groups.) If you do not use a role that always exists, then when the creating role is dropped the created role will lose part of its administrative -privilege and will no longer be able to use the PRIMEDB tools to +privilege and will no longer be able to use the SokweDB tools to create users. -Hint: Use Unix privilege escalation techniques to execute the PRIMEDB +Hint: Use Unix privilege escalation techniques to execute the SokweDB command line tool in an environment that gives the tool access to the PostgreSQL_ superuser. -- 2.34.1