Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   14857 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

SSS_DEBUGLEVEL(8)	       SSSD Manual pages	     SSS_DEBUGLEVEL(8)

NAME
       sss_debuglevel - change debug level while SSSD is running

SYNOPSIS
       sss_debuglevel [options] NEW_DEBUG_LEVEL

DESCRIPTION
       sss_debuglevel changes debug level of SSSD monitor and providers to
       NEW_DEBUG_LEVEL while SSSD is running.

OPTIONS
       -c,--config
	   Specify a non-default config file. The default is
	   /etc/sssd/sssd.conf. For reference on the config file syntax and
	   options, consult the sssd.conf(5) manual page.

       NEW_DEBUG_LEVEL
	   Bit mask that indicates which debug levels will be visible. 0x0010
	   is the default value as well as the lowest allowed value, 0xFFF0 is
	   the most verbose mode. This setting overrides the settings from
	   config file.

	   Currently supported debug levels:

	   0x0010: Fatal failures. Anything that would prevent SSSD from
	   starting up or causes it to cease running.

	   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.

	   0x0040: Serious failures. An error announcing that a particular
	   request or operation has failed.

	   0x0080: Minor failures. These are the errors that would percolate
	   down to cause the operation failure of 2.

	   0x0100: Configuration settings.

	   0x0200: Function data.

	   0x0400: Trace messages for operation functions.

	   0x1000: Trace messages for internal control functions.

	   0x2000: Contents of function-internal variables that may be
	   interesting.

	   0x4000: Extremely low-level tracing information.

	   To log required 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: This is new format of debug levels introduced in 1.7.0. Older
	   format (numbers from 0-10) is compatible but deprecated.

SEE ALSO
       sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5),
       sssd-ipa(5), sssd-ad(5), sssd-sudo(5),sss_cache(8), sss_debuglevel(8),
       sss_groupadd(8), sss_groupdel(8), sss_groupshow(8), sss_groupmod(8),
       sss_useradd(8), sss_userdel(8), sss_usermod(8), sss_obfuscate(8),
       sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8),
       sss_ssh_knowhostsproxy(8),pam_sss(8).

AUTHORS
       The SSSD upstream - http://fedorahosted.org/sssd

SSSD				  05/28/2013		     SSS_DEBUGLEVEL(8)

Vote for polarhome