11-29-2007
HP-UX system information
Hi,
I'm writing a script to display a lot of information which describe a server (OS distrib, release, Hardware platform, CPU, HD, S/N...).
For Linux side it is ok as you have almost all the information in /proc/cpuinfo, /proc/meminfo... and you can use dmidecode but for HP-UX I didn't find such files and command.
Could you please help me?
Best regards
biker007fr
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm just getting started with unix and would like to know 1) how to tell how big the harddrive is 2) how to tell if there are multiple harddrive installed on the machine 3) a relitavely easy way to tell what programs are installed on the machine.
I'm using Sun OS 5.6
Thanks (3 Replies)
Discussion started by: ViperD
3 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
I am new to Unix and am working on AIX ( rs6000 ). I am looking for the system info of the unix box like
1. Number of CPUs
2. CPU speed
3. RAM size
Your help is much appreciated
Thanks
rao. (6 Replies)
Discussion started by: rao
6 Replies
3. HP-UX
How do I get the system information on a HP UNIX server. details like CPU speed, number of processors etc. (4 Replies)
Discussion started by: Olamide
4 Replies
4. Shell Programming and Scripting
hi
I am new to this forum. hope to get help from u all.
how can i write these by using shell programming?
1. The name of the machine and the date/time at which the report was produced.
2. Licensing information such as the operating system revision level and license restrictions in terms of... (1 Reply)
Discussion started by: nokia1100
1 Replies
5. Shell Programming and Scripting
Hey,
I am after the commands to get the following information for my Unix system:
default visual editor (i dont even know where to start with this one)
default window manager (this one either, no idea)
total quota (just the size, none of the other data. I've narrowed it down to quota -sv)... (1 Reply)
Discussion started by: bonjour
1 Replies
6. AIX
Hi,
How to get the AIX system hardware and software basic information using terminal command with guest login?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS Configuration:
... (4 Replies)
Discussion started by: forumguest
4 Replies
7. Infrastructure Monitoring
Hi,
How to get the Linux system hardware and software basic information using terminal command ?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS Configuration:
OS Build Type:... (6 Replies)
Discussion started by: forumguest
6 Replies
8. Solaris
Hi,
How to get the Solaris system hardware and software basic information using terminal command with guest login?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS Configuration:
... (15 Replies)
Discussion started by: forumguest
15 Replies
9. BSD
Hi,
How to get the FreeBsd system hardware and software basic information using terminal command with guest login?
Here below i have specified some of the information i need. Please have a look at this and guide me.
OS Name:
OS Version :
OS Manufacturer:
OS... (2 Replies)
Discussion started by: forumguest
2 Replies
10. AIX
Hi all,
I have googled around quite a bit and tried many different commands to get system information about my AIX 5.3 box but none of the commands I've used have given me quite what I'm looking for. I am interested in finding out the model of the motherboard, and amount of available RAM, the... (2 Replies)
Discussion started by: ThePistonDoctor
2 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)