Sponsored Content
Full Discussion: best monitoring solution
Special Forums Cybersecurity best monitoring solution Post 302259980 by joquendo on Wednesday 19th of November 2008 11:24:52 AM
Old 11-19-2008
You may want to take a look at ZenOSS and use it as a standalone, or combined with Splunk
 

2 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

How to install Cacti (a system monitoring and graphing solution) with Nginx?

Here's a short tutorial on installing Cacti with Nginx on Linux. (0 Replies)
Discussion started by: notblog
0 Replies

2. UNIX for Advanced & Expert Users

Monitoring Solution

Hi Our organization has a lot of IT systems ( OLTP, MIS, Exadata, EMV, noncore ... ) - running diferrent platforms ( AIX, Linux, Sun, Win Server, ...), each system has its own monitoring tool designed by its manufacturer. We also write some shell scripts to do it manually. But we... (3 Replies)
Discussion started by: bobochacha29
3 Replies
sys_attrs_gpc_input(5)						File Formats Manual					    sys_attrs_gpc_input(5)

NAME
sys_attrs_gpc_input - gpc_input subsystem attributes DESCRIPTION
This reference page lists and describes attributes for the GPC Input (gpc_input) kernel subsystem. This subsystem handles mouse and key- board input for both old style LK* keyboards and serial mice, and the newer PC-style (PS/2) keyboards and mice. In all supported scan code- sets, unique single-byte scan codes differentiate the standalone Insert, Home, Page Up, Page Down, Delete, and End keys from the same keys on the numeric keypad (with Num Lock toggled to off). Refer to the sys_attrs(5) reference page for an introduction to the topic of kernel subsystem attributes. The gpc subsystem has a number of visible attributes. Of these, only the following should ever be modified: A value that identifies the scan codeset generated by the keyboard. Only two values are supported for this attribute. The scan code- sets that these values identify differ in how internal keyboard hardware distinguishes between the numeric keypad's Up Arrow (entered with with Num Lock toggled off) and the standalone Up Arrow key. Keyboard hardware sends different single-byte scan codes to distinguish the standalone Up Arrow and the Up Arrow entered through the numeric keyboard (with Num Lock toggled off). Keyboard hardware sends two bytes for the standalone Up Arrow and a single-byte scan code for the Up Arrow entered through the numeric key- board. These values are intended to be set by system software, not users. Although both values (scan codesets) work with most of the Compaq keyboards (both LK* and PC-style) used with Tru64 UNIX systems, 3 identifies the scan codeset that is most efficient for these key- boards. The keyboard of the AlphaBook (laptop) computer is the only supported keyboard that requires the 2 setting. The scan code- sets identified by these values may work with other (third-party) keyboards; however, Compaq does not test or support other key- boards for use with Tru64 UNIX systems. It is possible to set kbd_scancode to a 0 or 1 value. These values are currently undefined and will result in one of the following console errors: gpc_input_configure: scan code not supported ps2_input_configure: scan code not supported These errors are displayed independently of the setting for the gpc_developer_debug attribute. Enables (1) or disables (0) boot- and run-time console messages used by systems programmers to debug device driver configuration problems. Default value: 0 (disabled) SEE ALSO
sys_attrs(5) sys_attrs_gpc_input(5)
All times are GMT -4. The time now is 07:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy