Hello, every one,
I tried to install redhat linux enterprise server version 4 (ES4) on the my system with the
following configuration
Pentium core 2 duo 2.66 E 6750
Intel DG33FB motherboard
160Gb Segate hard disk (SATA)
1024 mb (1GB) DDR2 TRAN RAM
Lg DVD/Cd WR
BUT AM GETTING... (0 Replies)
Dear Sir,
I am Shidlingayya India, i am new to unix script..my problem is
present-> I have to read the eeprom locations from 0 to 255 locations in separate file..i wrote the code for this as follows
@eep_save_all ;<filename> store eeprom data to intel hex file
kr 0,,02/n
wf %1,... (0 Replies)
Hi: I was setting up a modem on an Ultra5 running 2.6. (yes I know, how quaint)
There are 15 systems that are interlinked but not accessible to the outside world.
This will end soon with new updated sun systems but until then the system needs to be accessed by the outside world. Hence the... (1 Reply)
hello
i have sun machine and i need to reset EEPROM password where evrytime machine boot i should put password to start in booting
any one can help me how i can remove this password
Thanks (1 Reply)
Hi all,
So I have a binary file and I need to generate an expected EEPROM checksum for it. Ideally, I would like to input the file (with the path) and output a computed checksum. Ive been using (cksum file1) with no avail and I was just curious as to whether there is such thing as EEPROM... (1 Reply)
Hi all,
So I have a binary file and I need to generate an expected EEPROM checksum for it. Ideally, I would like to input the file (with the path) and output a computed checksum. Ive been using (cksum file1) with no avail and I was just curious as to whether there is such thing as EEPROM cksum,... (1 Reply)
I have a weird situation in which the binary dumps core and gives bus error. But before dumping the core and throwing the buss error, it gives some output.
unfortunately I can't grep the output before core dump
db2bfd -b test.bnd
maxSect 15
Bus Error (core dumped)
But if I do ... (4 Replies)
Hello all,
I am currently trying to find a solution to replacing some 10 year old Solaris boxes because it is obvious that they are going to fail soon. The problem is that they are license servers, and I need the eeprom serial to transfer to a new computer. Now, I could request that we get new... (1 Reply)
Discussion started by: DeanCarlo
1 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)