:confused:
I have put together an old machine with a 386DX CPU (40MHz)
with 8Mb of RAM and a 160Mb hard disk. One guy told me that its still suitable for UNIX. Can enyone give me some hints on how to start? (1 Reply)
I just installed FreeBSD 4.5 and I want to find out how I can start and run X? When I boot I get taken to the command line. Xconfigurator doesn't want to work. (2 Replies)
I've installed Fedora Core 2 on a machine on my home network. X Windows (GNOME) is set up and works correctly, when I log in from the console.
However, when using Cygwin X from a different machine and trying to start an X session using startx it gives me the following error
That makes sense... (2 Replies)
I am re-learning UNIX and want to download Unix to my lab for studying on the road. Any suggestions? Got several books, but need to run scripts :rolleyes: (2 Replies)
Hi,
While I am trying SFTP my machine to another unix machine ,
it was working fine till 10 min back.
But now i am getting the below error
"Request for subsystem 'sftp' failed on channel 0"
Could you please someone help me to solve or analyise the root cause...
Cheers:b:,
Mahiban (0 Replies)
Hi,
i got the following error when i tried to access the cygwin x server from a windows XP PC.
"xdmcp fatal error session failed session 23 failed for display"
Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Hi to all,
I'm started to write some very simple loops in bash an i'm getting this error
-bash:
(the example is just to show when the error appeared)
the code was
x=o
while
do
echo "hello"
x++
done (5 Replies)
I'm authenticating with SSSD / Kerberos against Windows Server 2012 R2. I've setup credentails delegation using these options:
Host *
GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes
GSSAPITrustDns yes
For both client/server but no luck. I've read online that I need to run... (2 Replies)
e.g.
File name: File.txt
cat File.txt
Result:
#INBOUND_QUEUE=FAQ1
INBOUND_QUEUE=FAQ2
I want to get the value for one which is not commented out.
Thanks, (3 Replies)
So, I wanted to see if I could just use X without a desktop. I installed Debian from a netinstall on a vm and installed xorg with apt. Logged in as a normal user with startx and had a big black background. Seemed like everything was working as expected, so I went to configure tint2 at start up. I... (3 Replies)
Discussion started by: Azrael
3 Replies
LEARN ABOUT CENTOS
sss_debuglevel
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
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).
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.
Default: 0
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_knownhostsproxy(8),pam_sss(8).
AUTHORS
The SSSD upstream - http://fedorahosted.org/sssd
SSSD 06/17/2014 SSS_DEBUGLEVEL(8)