01-05-2018
Please show the contents of dfoutput.csv and a (partial) hexdump of it. I guess the problem might be on the receiving side. What's your mail client?
7 More Discussions You Might Find Interesting
1. Red Hat
Hi,
I have monitored that disk utilization is very high on one of red hat linux VM.
Would like to know how to find out that issue of high disk utilization is because of disk or Installed Application on that server is causing the problem.
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
2. Infrastructure Monitoring
Dear Gentleman
in my environment I have Solaris10 OS Box in Global Zone with 136 GB and mount point from SAN Storage 500 GB (Orastorage)
Zone1 mounted on /Zones folder with 66 GB
when I run zpool list output
-bash-3.00$ zpool list
NAME SIZE ALLOC FREE CAP HEALTH... (0 Replies)
Discussion started by: Hosam
0 Replies
3. Red Hat
Hi,
Can anybody explain why my newly created 120G FS shows 100% utilization when only 113G of disk space has been used? ......
# df -h .
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg01-lvol0
119G 113G 0 100% /u02
#du -h /u02
16K ... (3 Replies)
Discussion started by: Duffs22
3 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I have hundred folders under a fs /apps which is used by different users and they upload their data to these folders on a daily basis.
Using du -sk gives me complete structure of the filesystem but i want to find out day to day utlization of the top ten highest accoriding to size wise
... (4 Replies)
Discussion started by: chetansingh23
4 Replies
5. Shell Programming and Scripting
Below script perfectly works, giving below mail output. BUT, I want to make the script mail only if there are any D-Defined/T-Transition/B-Broken State WPARs and also to copy the output generated during monitoring to a temporary log file, which gets cleaned up every week. Need suggestions.
... (4 Replies)
Discussion started by: aix_admin_007
4 Replies
6. Shell Programming and Scripting
I have the below script
i am getting the csv in garbled format.Please suggest the changes.
SUNOS
#######################################################################
####MAIN SCRIPT
#######################################################################
today=`date "+%m-%d-%Y ... (3 Replies)
Discussion started by: rafa_fed2
3 Replies
7. UNIX for Beginners Questions & Answers
I have prepared script which will collect cpu, memory and df out out for multiple server and send in one mail, but my script only run in one server, and when I send to mail, it shows in text format. it should be show actual format.
if any one can help , that would be very grateful.
script... (1 Reply)
Discussion started by: yash_message
1 Replies
DDB(8) BSD System Manager's Manual DDB(8)
NAME
ddb -- configure DDB kernel debugger properties
SYNOPSIS
ddb capture [-M -core] [-N -system] print
ddb capture [-M -core] [-N -system] status
ddb script scriptname
ddb script scriptname=script
ddb scripts
ddb unscript scriptname
ddb pathname
DESCRIPTION
The ddb utility configures certain aspects of the ddb(4) kernel debugger from user space that are not configured at compile-time or easily
via sysctl(8) MIB entries.
To ease configuration, commands can be put in a file which is processed using ddb as shown in the last synopsis line. An absolute pathname
must be used. The file will be read line by line and applied as arguments to the ddb utility. Whitespace at the beginning of lines will be
ignored as will lines where the first non-whitespace character is '#'.
OUTPUT CAPTURE
The ddb utility can be used to extract the contents of the ddb(4) output capture buffer of the current live kernel, or from the crash dump of
a kernel on disk. The following debugger commands are available from the command line:
capture [-M core] [-N system] print
Print the current contents of the ddb(4) output capture buffer.
capture [-M core] [-N system] status
Print the current status of the ddb(4) output capture buffer.
SCRIPTING
The ddb utility can be used to configure aspects of ddb(4) scripting from user space; scripting support is described in more detail in
ddb(4). Each of the debugger commands is available from the command line:
script scriptname
Print the script named scriptname.
script scriptname=script
Define a script named scriptname. As many scripts contain characters interpreted in special ways by the shell, it is advisable to
enclose script in quotes.
scripts
List currently defined scripts.
unscript scriptname
Delete the script named scriptname.
EXIT STATUS
The ddb utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
The following example defines a script that will execute when the kernel debugger is entered as a result of a break signal:
ddb script kdb.enter.break="show pcpu; bt"
The following example will delete the script:
ddb unscript kdb.enter.break
For further examples, see the ddb(4) and textdump(4) manual pages.
SEE ALSO
ddb(4), textdump(4), sysctl(8)
HISTORY
The ddb utility first appeared in FreeBSD 7.1.
AUTHORS
Robert N M Watson
BUGS
Ideally, ddb would not exist, as all pertinent aspects of ddb(4) could be configured directly via sysctl(8).
BSD
December 24, 2008 BSD