Sponsored Content
Full Discussion: Auditing Sun Servers
Operating Systems Solaris Auditing Sun Servers Post 302681379 by vmcore on Friday 3rd of August 2012 10:17:06 AM
Old 08-03-2012
There will be as many way to do this as there are people willing to post anything here. If you have access to Oracle/Sun Explorer data collection, I would download that bundle and test it on server of your choice.
This explorer, tool, is designed to collect a lot of statistics/inventory when it is run on Solaris OS, version is not important. It will collect all you have listed above, but you will be required to pull specific data out of collections. Data is presented to you in a plain txt, so it is easy to read.
Also, EXP data is good to keep for future reference, comparing before and after patching if needed.

Oracle Services Tools Bundle (STB) - RDA/Explorer, SNEEP, ACT (Doc ID 1153444.1)

Hope it helps.
 

9 More Discussions You Might Find Interesting

1. Solaris

identifying Tape drives on Sun Servers

Hi, Can you please help me to locate tape drives on Sun Server and the capacity of the tape drive. I am managing a Sun 4u server. Need this urgently. Regards, Vivek (2 Replies)
Discussion started by: vivek_scv
2 Replies

2. UNIX for Advanced & Expert Users

Default ALOM username and password for the Sun servers

Hi, Anyone please tell me the default ALOM username and password for the sun server(Sun fire V210). Thanks muthu (1 Reply)
Discussion started by: muthulingaraja
1 Replies

3. Solaris

Windows AD for Sun Solaris Servers

Hi All I have a few sun servers(5.9) on xyz.com domain. I have to integrate these servers with the Windows AD of another domain,say abc.com. My sun servers should use the AD of abc.com for user authentication. I am thinking of implementing NIS. But not too sure whether it will work. Can... (3 Replies)
Discussion started by: efunds
3 Replies

4. UNIX for Advanced & Expert Users

File Auditing in Sun Solaris environment

Hi All, I have a requirement to report us on changing a group of static files. Those are the binary files that run in Production every day. Due to the in sercure environment situations, I found many are indulging in there own changes to the binaries by doing some changes in the souce code. ... (1 Reply)
Discussion started by: mohan_kumarcs
1 Replies

5. Solaris

Cannot get my Sun Solaris servers to log into Brocade Switch

Cannot get my Sun Solaris servers to log into a Brocade 5100. All fiber has been connected correctly and all drivers and firmware are loaded and up to date according to EMCGrab report. Below is an output from server. Please Help: HBA Port WWN: 2100001b321063c4 OS Device Name: /dev/cfg/c3... (2 Replies)
Discussion started by: sbkilbride
2 Replies

6. Shell Programming and Scripting

Script to monitor sun servers temperature

Dears, need help on developing a script to monitor sun server temperature , I'm using the below command to check the servers one by one /usr/platform/`uname -i`/sbin/prtdiag -v Servers Models are : 2 x Sun SPARC Enterprise M9000 Server 4 x Sun Fire V490 2 x Sun Blade T6300 Server... (1 Reply)
Discussion started by: bejo4ever
1 Replies

7. Solaris

ILOM Banner Sun x41XX servers

Is it possible to set the information that shows in the cli banner when you login to the ILOM? In addition, after I set the hostname of the ILOM, how do I check it? (2 Replies)
Discussion started by: brialt1
2 Replies

8. UNIX for Advanced & Expert Users

Sun M5000 servers diaster recovery plan

Hi, We have two Sun M5000 systems. A is Oracle server and B is testing server. There are nine Solaris 10 zones set on A. SAN is connecting to A with ZFS configuration. Now we want to set B to be a backup server of A and make the two as identical as possible. No VERITAS cluster, no Solaris... (3 Replies)
Discussion started by: aixlover
3 Replies

9. Solaris

sun servers currently used

can anybody give me a list of sun servers currently being used in the industry (5 Replies)
Discussion started by: veritas
5 Replies
SYSTEMD-READAHEAD-REPLAY.SERVICE(8)			 systemd-readahead-replay.service		       SYSTEMD-READAHEAD-REPLAY.SERVICE(8)

NAME
systemd-readahead-replay.service, systemd-readahead-collect.service, systemd-readahead-done.service, systemd-readahead-done.timer, systemd- readahead - Disk read ahead logic SYNOPSIS
systemd-readahead-replay.service systemd-readahead-collect.service systemd-readahead-done.service systemd-readahead-done.timer /usr/lib/systemd/systemd-readahead/systemd-readahead [OPTIONS...] COMMAND [DIRECTORY | FILE] DESCRIPTION
systemd-readahead-collect.service is a service that collects disk usage patterns at boot time. systemd-readahead-replay.service is a service that replays this access data collected at the subsequent boot. Since disks tend to be magnitudes slower than RAM, this is intended to improve boot speeds by pre-loading early at boot all data on disk that is known to be read for the complete boot process. systemd-readahead-done.service is executed a short while after boot completed and signals systemd-readahead-collect.service to end data collection. On this signal, this service will then sort the collected disk accesses and store information about them in /.readahead. Normally, both systemd-readahead-collect.service and systemd-readahead-replay.service are activated at boot so that access patterns from the preceding boot are replayed and new data collected for the subsequent boot. However, on read-only media where the collected data cannot be stored, it might be a good idea to disable systemd-readahead-collect.service. On rotating media, when replaying disk accesses at early boot, systemd-readahead-replay.service will order read requests by their location on disk. On non-rotating media, they will be ordered by their original access timestamp. If the file system supports it, systemd-readahead-collect.service will also defragment and rearrange files on disk to optimize subsequent boot times. OPTIONS
systemd-readahead understands the following options: -h, --help Prints a short help text and exits. --max-files= Maximum number of files to read ahead. Only valid for thes collect command. --file-size-max= Maximum size of files in bytes to read ahead. Only valid for the collect and replay commands. --timeout= Maximum time in microseconds to spend collecting data. Only valid for the collect command. COMMANDS
The following commands are understood by systemd-readahead: collect [DIRECTORY] Collect read-ahead data on early boot. When terminating, it will write out a pack file to the indicated directory containing the read-ahead data. replay [DIRECTORY] Perform read-ahead on the specified directory tree. analyze [FILE] Dumps the content of the read-ahead pack file to the terminal. For each file, the output lists approximately how much will be read ahead by the replay command. SEE ALSO
systemd(1) systemd 208 SYSTEMD-READAHEAD-REPLAY.SERVICE(8)
All times are GMT -4. The time now is 06:06 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy