Sponsored Content
Full Discussion: Can anyone explain this line
Top Forums UNIX for Dummies Questions & Answers Can anyone explain this line Post 302878540 by ramky79 on Friday 6th of December 2013 03:44:12 PM
Old 12-06-2013
Thank you joeyg and Don Cragun for the wonderful explanation; However what could be the reasons when you dont require coloring, can you explain a scenario where coloring helps..
To me without understanding the concept behind coloring ; it simply looks to me as adding unnecessary complexity to the code.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Please explain this command line ?

Please explain this command line ? wc<infile<newfile Thanx, Saneesh Joseph. (2 Replies)
Discussion started by: saneeshjose
2 Replies

2. Shell Programming and Scripting

can anyone explain this?

:start /@~/{ h s/\(.*\)@~.*$/\1/ s/@~$// s/@~/\ /g p g s/.*@~\(.*\)/\1/ } //{ N s/\n/ / b start } (2 Replies)
Discussion started by: djkane
2 Replies

3. UNIX for Dummies Questions & Answers

Explain the line "mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'`"

Hi Friends, Can any of you explain me about the below line of code? mn_code=`env|grep "..mn"|awk -F"=" '{print $2}'` Im not able to understand, what exactly it is doing :confused: Any help would be useful for me. Lokesha (4 Replies)
Discussion started by: Lokesha
4 Replies

4. Shell Programming and Scripting

Please can any one explain this ${0##/}

I did not understand what is ${0##/} PGM=${0##/} TMP=/tmp/${PGM}.$$ Please explain me. (2 Replies)
Discussion started by: gadege
2 Replies

5. Shell Programming and Scripting

please explain the below

could u please convert the below statement to shell script ---------- logdir=/smp/dyn/logfiles/cpm/pgm/pgIm $logdir = $logdir ."/pgIm${toDate}*"; ---- could u please explain the below clearly grep -i adding $logdir | grep -iv equation | awk '{print \$NF}' | sort -u | sed -e... (1 Reply)
Discussion started by: mail2sant
1 Replies

6. AIX

can anyone explain this?

this is the mksys b script.... can anyone explain .. what # and 1 in if condition this is the first line of the script... it is not from middle of the script.... if then echo "Not enough parameters, need a client name for mksysb" Usage="Usage: $0 <client name>" ... (2 Replies)
Discussion started by: honeym210
2 Replies

7. Homework & Coursework Questions

Could anyone help explain this?

1. The problem statement, all variables and given/known data: I have a retake assignment to complete for my computer networks and OS class. This isn't really my area, had I known last year I could have swapped it for a different module I would have done so. I'm determined to get through it... (6 Replies)
Discussion started by: Squall Moogle
6 Replies

8. Shell Programming and Scripting

Explain $# please

I'm trying to follow a script and I see it begins with this: if ; then if ; then print "blah $0 blah blah " exit fi fi What does $# mean? I found out that $1 refers to the shell environment and the last argument that was entered or passed in the previous command. I couldn't find $#... (2 Replies)
Discussion started by: MaindotC
2 Replies

9. Shell Programming and Scripting

anyone can explain this?

why the case 2 will happen ? , ' should stop the history substitution ,shouldn't it? case 1 # echo "123"|sed '/123/!d' 123 case 2 # echo "123 > 456 > 1 > "|sed '/123/!d' -bash: !d': event not found case 3 # echo "123 > 456 > 12 > "|sed '/123/'\!d 123 # bash --version (1 Reply)
Discussion started by: justlooks
1 Replies

10. UNIX for Dummies Questions & Answers

How I can explain this?

Hi friends! I'm learning UNIX and I have a small question. Working with Shell, i put the name of one executable (in c language) + one number and it says this: $ gcc misterioso_4.c $ ./misterioso_4 6 got: , I can not find an answer in the manual because I havent applied any variable.... (5 Replies)
Discussion started by: dakota
5 Replies
ATOPRC(5)							File Formats Manual							 ATOPRC(5)

NAME
atoprc - atop/atopsar related rcfile DESCRIPTION
This manual page documents the rcfile of the atop and atopsar commands. These commands can be used to monitor the system and process load on a Linux system. The atoprc file contains the default settings. These settings are read during startup, first from the system-wide rcfile /etc/atoprc and after that from the user-specific rcfile ~/.atoprc (so system-wide settings can be overruled by an individual user). The options in both rcfiles are identical. OPTIONS
The rcfile contains keyword-value pairs, one on every line (blank lines and lines starting with a #-sign are ignored). The following keywords can be specified: flags A list of default flags for atop can be defined here. The flags which are allowed are 'g', 'm', 'd', 'n', 'u', 'p', 's', 'c', 'v', 'C', 'M', 'D', 'N', 'A', 'a', 'f', '1' and 'x'. interval The default interval value in seconds. linelen The length of a screen line when sending output to a file or pipe (default 80). username The default regular expression for the users for which active processes will be shown. procname The default regular expression for the process names to be shown. maxlinecpu The maximum number of active CPU's that will be shown. maxlinelvm The maximum number of active logical volumes that will be shown. maxlinemdd The maximum number of active multiple devices that will be shown. maxlinedisk The maximum number of active disks that will be shown. maxlineintf The maximum number of active network interfaces that will be shown. cpucritperc The busy percentage considered critical for a processor (see section COLORS in the man-page of the atop command). This percentage is used to determine a weighted percentage for line coloring and sorting of active processes. When this value is zero, no line coloring or automatic sorting is performed for this resource. dskcritperc The busy percentage considered critical for a disk (see section COLORS in the man-page of the atop command). This percentage is used to determine a weighted percentage for line coloring and sorting of active processes. When this value is zero, no line coloring or automatic sorting is performed for this resource. netcritperc The busy percentage considered critical for a network interface (see section COLORS in the man-page of the atop command). This per- centage is used to determine a weighted percentage for line coloring and sorting of active processes. When this value is zero, no line coloring or automatic sorting is performed for this resource. memcritperc The percentage considered critical for memory utilization (see section COLORS in the man-page of the atop command). This percentage is used to determine a weighted percentage for line coloring and sorting of active processes. When this value is zero, no line coloring or automatic sorting is performed for this resource. swpcritperc The occupation percentage considered critical for swap space (see section COLORS in the man-page of the atop command). This percentage is used to determine a weighted percentage for line coloring and sorting of active processes. When this value is zero, no line color- ing or automatic sorting is performed for this resource. swoutcritsec The number of pages swapped out per second considered critical for for memory utilization (see section COLORS in the man-page of the atop command). This threshold is used in combination with 'memcritperc' to determine a weighted percentage for line coloring and sort- ing of active processes. When this value is zero, no line coloring or automatic sorting is performed for this resource. almostcrit A percentage of the critical percentage to determine if the resource is almost critical (see section COLORS in the man-page of the atop command). When this value is zero, no line coloring for `almost critical' is performed. atopsarflags A list of default flags for atopsar can be defined here. The flags that are allowed are 'S', 'x', 'C', 'M', 'H', 'a', 'A' and the flags to select one or more specific reports. An example of the /etc/atoprc or ~/.atoprc file: flags Aaf interval 5 username procname maxlinecpu 4 maxlinedisk 10 maxlineintf 5 cpucritperc 80 almostcrit 90 atopsarflags CMH ownprocline PID:50 VGROW:40 RGROW:45 COMMAND-LINE:50 ownpagline PAGSCAN:3 BLANKBOX:0 PAGSWIN:3 PAGSWOUT:7 The keywords 'ownprocline' and 'ownpagline' are explained in the subsequent section. OWN DEFINITION OF OUTPUT LINE
Via the rcfile it is possible to define the layout of the output lines yourself, i.e. you can define the layout of one line with process information with the keyword 'ownprocline' (to be selected with the key 'o' or the flag -o) and you can redefine all lines with system information. The layout of an output-line can be defined as follows (notice that this should be specified as one line in the rcfile): keyword <columnid>:<prio> [<columnid>:<prio> ...] The columnid is the symbolic name of a column that should shown at this position in the output line. The prio is a positive integer value that determines which columns have precedence whenever not all specified columns fit into the current screen-width. The higher value, the higher priority. The column-specifications should be separated by a space. The order in which columns have been specified is the order in which they will be shown, with respect to their priority (columns that do not fit, will be dropped dynamically). A special columnid for system lines is 'BLANKBOX'. This indicates that an empty column is required at this position. Also this special columnid is followed by a priority (usually low). The following definition can be specified for process information: ownprocline The columnid's are the names of the columns that are shown in the normal output of the process-related lines that are shown by atop such as 'PID', 'CMD', 'S', .... The only exception is the special columnid 'SORTITEM' that is used to show one of the columns CPU%/DSK%/MEM%/NET%, depending on the chosen sort-criterium. An example of a user-defined process line: ownprocline PID:20 PPID:10 SYSCPU:15 USRCPU:15 VGROW:14 VSIZE:12 RGROW:14 RSIZE:12 ST:8 EXC:7 S:11 SORTITEM:18 CMD:20 The following definitions are used internally by atop as the default system lines (you can redefine each of them in the rcfile as one line): ownsysprcline Redefinition of line labeled with 'PRC': ownsysprcline PRCSYS:8 PRCUSER:8 BLANKBOX:0 PRCNPROC:7 PRCNZOMBIE:5 PRCCLONES:4 BLANKBOX:0 PRCNNEXIT:6 ownallcpuline Redefinition of line labeled with 'CPU' for total CPU-utilization: ownallcpuline CPUSYS:8 CPUUSER:7 CPUIRQ:4 BLANKBOX:0 CPUIDLE:5 CPUWAIT:6 BLANKBOX:0 CPUSTEAL:1 CPUGUEST:3 ownonecpuline Redefinition of line labeled with 'CPU' for utilization of one CPU: ownonecpuline CPUISYS:8 CPUIUSER:7 CPUIIRQ:4 BLANKBOX:0 CPUIIDLE:5 CPUIWAIT:6 BLANKBOX:0 CPUISTEAL:1 CPUIGUEST:3 owncplline Redefinition of line labeled with 'CPL': owncplline CPLAVG1:4 CPLAVG5:3 CPLAVG15:2 BLANKBOX:0 CPLCSW:6 CPLINTR:5 BLANKBOX:0 CPLNUMCPU:1 ownmemline Redefinition of line labeled with 'MEM': ownmemline MEMTOT:2 MEMFREE:5 MEMCACHE:3 MEMDIRTY:1 MEMBUFFER:3 MEMSLAB:3 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 ownswpline Redefinition of line labeled with 'SWP': ownswpline SWPTOT:3 SWPFREE:4 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 SWPCOMMITTED:5 SWPCOMMITLIM:6 ownpagline Redefinition of line labeled with 'PAG': ownpagline PAGSCAN:3 PAGSTALL:1 BLANKBOX:0 PAGSWIN:4 PAGSWOUT:3 owndskline Redefinition of lines labeled with 'LVM', 'MDD' and 'DSK': owndskline DSKNAME:8 DSKBUSY:7 DSKNREAD:6 DSKNWRITE:6 DSKKBPERRD:4 DSKKBPERWR:4 DSKMBPERSECRD:5 DSKMBPERSECWR:5 DSKAVQUEUE:1 DSKAVIO:5 ownnettrline Redefinition of line labeled with 'NET' for transport: ownnettrline NETTRANSPORT:9 NETTCPI:8 NETTCPO:8 NETUDPI:8 NETUDPO:8 NETTCPACTOPEN:6 NETTCPPASVOPEN:5 NETTCPRETRANS:4 NETTCPIN- ERR:3 NETTCPORESET:20 NETUDPNOPORT:1 NETUDPINERR:3 ownnetnetline Redefinition of line labeled with 'NET' for network: ownnetnetline NETNETWORK:5 NETIPI:4 NETIPO:4 NETIPFRW:4 NETIPDELIV:4 BLANKBOX:0 BLANKBOX:0 BLANKBOX:0 NETICMPIN:1 NETICMPOUT:1 ownnetifline Redefinition of line labeled with 'NET' for interfaces: ownnetifline NETNAME:8 NETPCKI:7 NETPCKO:7 NETSPEEDIN:6 NETSPEEDOUT:6 NETCOLLIS:3 NETMULTICASTIN:2 NETRCVERR:5 NETSNDERR:5 NETR- CVDROP:4 NETSNDDROP:4 The lines above are shown in the order as shown by atop in combination with the -f flag (in a very wide window you should be able to see all of the columns). SEE ALSO
atop(1), atopsar(1), logrotate(8) http://www.atoptool.nl AUTHOR
Gerlof Langeveld (gerlof.langeveld@atoptool.nl) JC van Winkel (jc@ATComputing.nl) AT Computing April 2010 ATOPRC(5)
All times are GMT -4. The time now is 10:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy