Sponsored Content
Full Discussion: Server inventory software
Top Forums UNIX for Advanced & Expert Users Server inventory software Post 302964330 by cjcox on Wednesday 13th of January 2016 01:50:18 PM
Old 01-13-2016
Best one is the one I wrote for IBM. But they'll never let you have it.

ZenOSS is a popular choice. If you use ServiceNow, they are touting their new discovery product. Dell's KACE might be interesting... there's a ton of products to look at and evaluate.
This User Gave Thanks to cjcox For This Post:
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Software Inventory

How can I find out what software is installed on the machine, other than ls? Is there a registry program like in Windows? The os is Sun 2.5. Thanks (1 Reply)
Discussion started by: ViperD
1 Replies

2. UNIX for Advanced & Expert Users

Collecting software inventory

how to obtain/ collect a list of all the applications installed in the system.. is there a configuration file(like the one which exists for hardware ) which holds all this information?? if no is there any command/shell script or utility that we can use for the same ?? I am using Red hat linux... (2 Replies)
Discussion started by: superghost
2 Replies

3. UNIX for Dummies Questions & Answers

Utilities/Scipts to Inventory Hardware and Software

Hi All, I am looking for a way to inventory the hardware and software components of many Solaris 8 servers/workstations. I would like to script this to run against a list of IP's in a text file. For Windows there are many such programs available (like Belarc) Is there anything similar for... (4 Replies)
Discussion started by: limey
4 Replies

4. Shell Programming and Scripting

Shell Scripts for automating server inventory for unix servers

Dear Team, I am very new to shell scripting & and presently monitoring unix boxes I am looking for a shell script which will give me the below output script should contain - hostname,OS Version,CPU details, Physical Memory, Partitions Details, Network Details and Software Installed,... (5 Replies)
Discussion started by: whizkidash
5 Replies

5. UNIX for Advanced & Expert Users

perl and HP-UX : instmodsh in combination with software depot : update inventory for installed Perl

we create a HP-UX software depot with a new perl-modul. after installation of the software depot, the perl module i can't find with instmodsh in the inventory for installed Perl modules. - i have learned of using instmodsh command : i find out what modules are already installed on my system. ... (0 Replies)
Discussion started by: bora99
0 Replies

6. Solaris

Server and Software upgrade

Hi Experts, we are planning to upgrade the End of life servers to new servers and from solaris 8/9 to 11. Server loads are minimum and not heavily loaded. After analysis we came to conclusion to use the below. Can experts out there please let me know whether it make sense or any way we can... (3 Replies)
Discussion started by: sundba
3 Replies

7. Solaris

Sun Server Hardware Inventory Details

How can I get the hardware inventory details of the Sun Servers like T5220 running Solaris 10? I would like to see the following details: 1. Chassis Information - Part Number, Serial Number etc. 2. Slots Present in the chassis 3. Modules/Cards equipped on the slots. Module details like Part... (8 Replies)
Discussion started by: baddy
8 Replies
cdtoc(4)                                                           File Formats                                                           cdtoc(4)

NAME
cdtoc - CD-ROM table of contents file DESCRIPTION
The table of contents file, .cdtoc, is an ASCII file that describes the contents of a CD-ROM or other software distribution media. It resides in the top-level directory of the file system on a slice of a CD-ROM. It is independent of file system format, that is, the file system on the slice can be either UFS or HSFS. Each entry in the .cdtoc file is a line that establishes the value of a parameter in the following form: PARAM=value Blank lines and comments (lines preceded by a pound-sign, ``#'') are also allowed in the file. Parameters are grouped by product, with the beginning of a product defined by a line of the form: PRODNAME=value Each product is expected to consist of one or more software packages that are stored together in a subdirectory on the distribution media. There can be any number of products described within the file. There is no required order in which the parameters must be specified, except that the parameters must be grouped by product and the PRODNAME parameter must appear first in the list of parameters for each product specified. Each parameter is described below. All of the parameters are required for each product. PRODNAME The full name of the product. This must be unique within the .cdtoc file and is preferably unique across all possi- ble products. This value may contain white space. The length of this value is limited to 256 ASCII characters; other restrictions may apply (see below). PRODVERS The version of the product. The value can contain any combination of letters, numbers, or other characters. This value may contain white space. The length of this value is limited to 256 ASCII characters; other restrictions may apply (see below). PRODDIR The name of the top-level directory containing the product. This name should be relative to the top-level directory of the distribution media, for example, Solaris_2.6/Product. The number of path components in the name is limited only by the system's maximum path name length, which is 1024 ASCII characters. Any single component is limited to 256 ASCII characters. This value cannot contain white space. The lengths of the values of PRODNAME and PRODVERS are further constrained by the fact that the initial install programs concatenate these values to produce the full product name. For unbundled products the combined length of the values of PRODNAME and PRODVERS must not exceed 256 ASCII characters. When you install OS services with Solstice Host Manager, directories for diskless clients are created by constructing names derived from a concatenation of the values of PRODNAME, PRODVERS, and client architecture, for example, /export/exec/Solaris_2.x_sparc.all/usr/platform. The length of the component containing the product name and version must not exceed 256 ASCII characters. Thus, for products corresponding to bundled OS releases (for example, Solaris 2.4), the values of PRODNAME and PRODVERS are effectively restricted to lengths much less than 256. The initial install programs use the value of the PRODDIR macro in the .cdtoc file to indicate where packages can be found. EXAMPLES
Example 1: Sample of .cdtoc file. Here is a sample .cdtoc file: # # .cdtoc file -- Online product family CD # PRODNAME=Online DiskSuite PRODVERS=2.0 PRODDIR=Online_DiskSuite_2.0 # PRODNAME=Online Backup PRODVERS=2.0 PRODDIR=Online_Backup_2.0 This example corresponds to the following directory layout on a CD-ROM partition: /.cdtoc /Online_DiskSuite_2.0 ./SUNWmddr.c ./SUNWmddr.m ./SUNWmddu /Online_Backup_2.0 ./SUNWhsm The bundled release of Solaris 2.6 includes the following .cdtoc file: PRODNAME=Solaris PRODVERS=2.6 PRODDIR=Solaris_2.6/Product This file corresponds to the following directory layout on slice 0 of the Solaris 2.6 product CD: /.cdtoc /Solaris_2.6/Product ./SUNWaccr ./SUNWaccu ./SUNWadmap . . . ./SUNWutool SEE ALSO
clustertoc(4), packagetoc(4), pkginfo(4) SunOS 5.10 14 Sept 2004 cdtoc(4)
All times are GMT -4. The time now is 03:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy