06-09-2019
Thanks Rudic & Peasant.
@Peasant - your solution worked awesome, didn't even take 1 second to finish a file.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm writing a bash script to log some selections from a sensors output (core temp, mb temp, etc.) and I would also like to have the current cpu usage as a percentage. I have no idea how to go about getting it in a form that a bash script can use. For example, I would simply look in the output of... (3 Replies)
Discussion started by: graysky
3 Replies
2. AIX
Hi Guys,
I need to write a script capable of identifying when a high cpu utilitzation process. It sounds simple but we are on a AIX 5.3 environment with Virtual CPU's (VP's) and logical CPU's. Please any ideas or tips would be highly appreciated. Thanks.
Harby. (6 Replies)
Discussion started by: arizah
6 Replies
3. Shell Programming and Scripting
Hi all
can any one help me to script monitoring
CPU load avg when reaches threshold value
and disk usage if it exceeds some %
tried using awk but when df -h out put is in two different lines awk doesnt work for the particular output in two different line ( output for df -h is in two... (7 Replies)
Discussion started by: robo
7 Replies
4. HP-UX
Hi Experts,
I am executing multiple instances(in parallel) of perl script on HP-UX box.
OS is allocating substantial amount of CPU to these perl processes,resulting higher cpu utilization.
Glance always shows perl processes are occupying majority of the CPU resource. It is causing slower... (2 Replies)
Discussion started by: sai_2507
2 Replies
5. Shell Programming and Scripting
I am looking for a way to log and graphically display cpu and RAM usage of linux processes over time. Since I couldn't find a simple tool to so (I tried zabbix and munin but installation failed) I started writing a shell script to do so
The script file parses the output of top command through... (2 Replies)
Discussion started by: andy_dufresne
2 Replies
6. Shell Programming and Scripting
Hi All,
I have a script which does report the cpu usuage, there are few output parameter/fields displayed from the script. My problem is I have monitor the output and decide
which cpu number (column 2) has maximum value (column 6).
Since the output is displayed/updated every seconds, it's very... (1 Reply)
Discussion started by: Optimus81
1 Replies
7. Shell Programming and Scripting
Hello Friends,
I am trying to create a shell script which will check the CPU utilization. I use command top to check the %CPU usage. It give s me below output
Cpu states:
CPU LOAD USER NICE SYS IDLE BLOCK SWAIT INTR SSYS
0 0.31 9.6% 0.0% 6.1% 84.3% 0.0% 0.0%... (3 Replies)
Discussion started by: Nakul_sh
3 Replies
8. Shell Programming and Scripting
Hi all
I was wondering if its possible to write a script to keep CPU usage at 90%-95%? for a single cpu linux server?
I have a perl script I run on servers with multple cpu's and all I do is max all but one cpu to get into the 90'% utilised area. I now need a script that raises the CPU to... (4 Replies)
Discussion started by: sudobash
4 Replies
9. Linux
Hi All,
Am very new to Linux and unix ...need below help .
need to list of process consuming more than 40% cpu and which are older than 10 days of a particular user ....
Thanks
V (4 Replies)
Discussion started by: venky456
4 Replies
10. Shell Programming and Scripting
I'm a newbie to shell scripting, I was given this script to modify. This script that monitors when CPU Usage is too high based off the top command. The comparison is not working as it should. Its comparing a decimal to a regualar interger. When it send me an email, it send an email and ignores the... (21 Replies)
Discussion started by: mhannor
21 Replies
flaw(7) Miscellaneous Information Manual flaw(7)
NAME
flaw - a Lua OO management framework for awesome WM widgets
DESCRIPTION
flaw stands for Fully Loaded AWesome. It is a LUA object oriented library providing a thin abstraction layer above awesome widgets. It is
aimed at being simple and resources efficient.
To achieve these goals, flaw provides the following concepts.
gadgets
To add functionality to awesome widgets, flaw defines gadget objects, which are a wrapper around a widget. All gadgets have proper-
ties, events, a refresh mechanism and a data provider (see below). Gadgets can wrap all awesome widget type, namely text boxes,
image boxes, graphs or progress bars. flaw provides many gadgets for common system information (like CPU or memory activity).
provider
flaw tries to minimise system access and data refresh. Since all information do not have the same expiration rate, all gadgets
refresh independently. And since some gadgets can share information, all data is provided by providers which can be shared among
gadgets. Providers maintain status data from the system and refreshes only when necessary (ie. when the gadget with the shortest
refresh rate demands it).
events Events are a way for the user to modify the gadget behaviour or properties when some conditions are met. An event is composed of a
trigger, which computes the condition, and an action. Event triggers are tested by the providers only when data changes. Both the
condition and the action are provided by the user.
USAGE
flaw depends on the lua-filesystem package which can be found http://luaforge.net/projects/luafilesystem. Once installed, the following
statement must be inserted in awesome configuration before any flaw gadget or mechanism is used.
require('flaw')
Using flaw consists in creating gadgets, passing them parameters to customize their display and events to add some behaviour to them, and
then adding them in a wibox like any other awesome widget. flaw and awful gadgets can live together. The complete flaw documentation is
available in Luadoc format. Enter the following command to generate it.
LUA_PATH="path_toflaw/doclet/html/?;;" luadoc -d html --nofiles *.lua
DIAGNOSTICS
flaw tries to recover upon bad invocations. When something wrong occurs, it outputs warning or error messages to stderr (for example, if
awesome was started with xsession, output will be found in ~/.xsession-errors ).
BUGS
Certainly a lot.
AUTHOR
David Soulayrol <david.soulayrol at gmail dot net>
SEE ALSO
awesome(1), awesome-client(1), awesomerc(5)
FEBRUARY 2009 flaw(7)