02-16-2012
10 More Discussions You Might Find Interesting
1. Programming
hi...
i need pointers to books/website...
'm trytin to write a daemon that monitors files of particular type(eg. text or pdfs) copied onto the hard disk. the daemon should detect the above n write the file name (along with the absolute path) to a file.
please DO NOT give me the code... (2 Replies)
Discussion started by: abhi_abhijith
2 Replies
2. Shell Programming and Scripting
#!/bin/bash
# Disk Space Monitoring for more than 95 %
# and Sending Alerts by Mail
if ;
then
`df -k |awk '$5 > 95 {print $1 " ----------- " $5}' |mailx -s "More than 95% disk usage in DEV" email@test.com';
else
exit 0
fi
I get the... (8 Replies)
Discussion started by: sriram003
8 Replies
3. Filesystems, Disks and Memory
Hi all,
I am looking for api to get me system monitoring statictics every 5 minutes.
I am looking at the following statistics:
1. System CPU Usage
2. Process CPU Usage
3. Process Memory Usage
4. I/O Usage for a certain disk.
5. Process I/O bytes/sec utilization.
I have seen very... (2 Replies)
Discussion started by: uiqbal
2 Replies
4. Shell Programming and Scripting
Hi All,
Just wanted to know if there is any way by which users can be notified about the failures in disks on Red Hat linux systems.
Thanks for all the help!!
nua7 (4 Replies)
Discussion started by: nua7
4 Replies
5. UNIX for Dummies Questions & Answers
Hi Guys,
I'm looking for a way to monitor disk health/status for a Solaris 5.8 sparc machine. I'm looking for something similar to LSIutility or MegaCLI.
Any suggestions?
Output of `modinfo`:
30 102616fb 10be8 118 1 ssd (SCSI SSA/FCAL Disk Driver 1.151)
122 7821c000 18550 32 1 ... (2 Replies)
Discussion started by: tank126
2 Replies
6. Shell Programming and Scripting
It's the old thread "Disk Space Monitoring Script", modified for UNIX
This is the new code:
df -k | awk ' { if ( int($4) > 90)
{subject = $1 " More than 90% disk usage. Used: " $4
email = "email@test.com"
print subject
cmd = "mailx -s \"" subject "\" " email
cmd | getline... (4 Replies)
Discussion started by: dungureanu
4 Replies
7. Shell Programming and Scripting
Hi All,
OS: Linux 86x64 bits Red Hat Linux
I get the email alert for the following when Alert condition is set for 30:
/dev/sda1 99M 21M 74M 22% /boot
-> Below 30%(Should not get the email alert)
Expected output as per E-Mail alert:
/dev/sda3 20G ... (2 Replies)
Discussion started by: a1_win
2 Replies
8. Shell Programming and Scripting
Unix box: solaris 5.8
Server: IP
Need to to set trap for cron job failures by writing a shell script (5 Replies)
Discussion started by: ChandruBala73
5 Replies
9. Solaris
Attempting to update an 11.0 server with many non-global zones installed. pkg publisher is pkg.oracle.com/solaris/support.
FMRI = pkg://solaris/entire@0.5.11,5.11-0.175.1.15.0.4.0:20131230T203500Z
When we run pkg update --accept the server contacts oracle, checks packages, finds about 700... (4 Replies)
Discussion started by: CptCarrot
4 Replies
10. UNIX for Beginners Questions & Answers
HI I am Trying to edit the below code to send email every day with difference of disk utilized in for last 24 hours but instead getting same usage everyday. can you please help me to point out where my calculation is going wrong. Thank you.
=================
#!/bin/bash
TODAY="at $(date... (0 Replies)
Discussion started by: Mi4304
0 Replies
LEARN ABOUT DEBIAN
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
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.
AUTHORS
The SSSD upstream - http://fedorahosted.org/sssd
SSSD
03/04/2013 SSS_DEBUGLEVEL(8)