- sss_override COMMAND [options]
Overrides data are stored in the SSSD cache. If the cache is deleted, all local overrides are lost. Please note that after the first override is created using any of the following user-add, group-add, user-import or group-import command. SSSD needs to be restarted to take effect. sss_override prints message when a restart is required.
Argument NAME is the name of original object in all commands. It is not possible to override uid or gid to 0.
user-add NAME [-n,--name NAME] [-u,--uid UID] [-g,--gid GID] [-h,--home HOME] [-s,--shell SHELL] [-c,--gecos GECOS]
- Override attributes of an user. Please be aware that calling this command will replace any previous override for the (NAMEd) user.
- Remove user overrides. However be aware that overridden attributes might be returned from memory cache. Please see SSSD option memcache_timeout for more details.
user-find [-d,--domain DOMAIN]
- List all users with set overrides. If DOMAIN parameter is set, only users from the domain are listed.
- Show user overrides.
Import user overrides from
FILE. Data format is similar to standard passwd file. The format is:
where original_name is original name of the user whose attributes should be overridden. The rest of fields correspond to new values. You can omit a value simply by leaving corresponding field empty.
- Export all overridden attributes and store them in FILE. See user-import for data format.
group-add NAME [-n,--name NAME] [-g,--gid GID]
- Override attributes of a group. Please be aware that calling this command will replace any previous override for the (NAMEd) group.
- Remove group overrides. However be aware that overridden attributes might be returned from memory cache. Please see SSSD option memcache_timeout for more details.
group-find [-d,--domain DOMAIN]
- List all groups with set overrides. If DOMAIN parameter is set, only groups from the domain are listed.
- Show group overrides.
Import group overrides from
FILE. Data format is similar to standard group file. The format is:
where original_name is original name of the group whose attributes should be overridden. The rest of fields correspond to new values. You can omit a value simply by leaving corresponding field empty.
- Export all overridden attributes and store them in FILE. See group-import for data format.
Those options are available with all commands.
SSSD supports two representations for specifying the debug level. The simplest is to specify a decimal value from 0-9, which represents enabling that level and all lower-level debug messages. The more comprehensive option is to specify a hexadecimal bitmask to enable or disable specific levels (such as if you wish to suppress a level).
Please note that each SSSD service logs into its own log file. Also please note that enabling "debug_level" in the "[sssd]" section only enables debugging just for the sssd process itself, not for the responder or provider processes. The "debug_level" parameter should be added to all sections that you wish to produce debug logs from.
In addition to changing the log level in the config file using the "debug_level" parameter, which is persistent, but requires SSSD restart, it is also possible to change the debug level on the fly using the sss_debuglevel(8) tool.
Currently supported debug levels:
0, 0x0010: Fatal failures. Anything that would prevent SSSD from starting up or causes it to cease running.
1, 0x0020: Critical failures. An error that doesn't kill the SSSD, but one that indicates that at least one major feature is not going to work properly.
2, 0x0040: Serious failures. An error announcing that a particular request or operation has failed.
3, 0x0080: Minor failures. These are the errors that would percolate down to cause the operation failure of 2.
4, 0x0100: Configuration settings.
5, 0x0200: Function data.
6, 0x0400: Trace messages for operation functions.
7, 0x1000: Trace messages for internal control functions.
8, 0x2000: Contents of function-internal variables that may be interesting.
9, 0x4000: Extremely low-level tracing information.
To log required bitmask debug levels, simply add their numbers together as shown in following examples:
Example: To log fatal failures, critical failures, serious failures and function data use 0x0270.
Example: To log fatal failures, configuration settings, function data, trace messages for internal control functions use 0x1310.
Note: The bitmask format of debug levels was introduced in 1.7.0.
The SSSD upstream - http://fedorahosted.org/sssd