similar to: 6310485 gcc and trapstat don''t get along

Author: elowe Repository: /hg/zfs-crypto/gate Revision: 1e626c708d19873645f833d0507362c3a5731c08 Log message: 6333712 SunFire 25K panics with IB card installed with HSI/P or ATM installed Files: update: usr/src/uts/sfmmu/vm/hat_sfmmu.c

Author: szhou Repository: /hg/zfs-crypto/gate Revision: 56b02c555bfb41a423c9856c46c8918128e9d3c1 Log message: PSARC 2005/373 Contract for the Miniroot Repository 6263254 console output gets graphically corrupted after the newboot 6270368 grub does not honor vendor option 150 to specify menu.lst file 6271324 boot-archive.xml is delivered into the wrong directory 6271395 grub should show progress

Hi all. We have a bunch of RHEL servers running Puppet. They are also connected to our Red Hat Satellite server. Currently we don''t have any master documentation system that stores all relevant information (i.e. type of server, hardware info, linux configuration, etc) about the servers. So what I''d like to do is implement some sort of system that can hold all this information.

Can dtrace help with collecting any of the following, in otherwords are there any existing counters to be exploited, or am I going to have to make my own custom Solaris build with additional counters... currently I can get this detailed trap information from our SPARC simulator, for example here are some ints-per-sec during a benchmark-of-interest: sending-source

Does anyone out there have any thoughts on the type of load common DTrace scripts would cause on a system if run 24x7? I know "common DTrace scripts" and their underlining probe calls a vague statement. So for the lack of a common and establish set of scripts in the OS, I''ll use the most popular right for my question...the DTraceToolkit from Brendan Gregg. Which by the