SysInfo requires a license file containing valid license information for permanent use. If no license is provided, then SysInfo will run in DEMO mode for 60 days. During the DEMO period, SysInfo will provide the same information as is provided with a full license, but it will display a warning message stating that it is running in DEMO mode. Once the DEMO period has been reached, SysInfo will display an error stating so and will exit without providing any system information.
There is one exception to requiring a license file. If your Internet domain name is one of the domains known to SysInfo to be used exclusively by non-profit educational institutions such as .edu, then no license file is required. In this case, SysInfo will function as if a license file is present. No additional licensing is required.
You can purchase SysInfo licenses by following these steps:
If you wish to install a license after you have already installed SysInfo, then use the following procedure:
Obtain a License if you do not already have one.
Install each license file you have by running the following command for each license file:
/opt/sysinfo/setup --licenseReplace /opt/sysinfo with the directory name where SysInfo is installed if different. You can also specify the name of the license file to install:
/opt/sysinfo/setup --license --licensefile file
You can verify your license information by running:
/opt/sysinfo/bin/mcsysinfo --licenseReplace /opt/sysinfo with the directory name where SysInfo is installed if different.
There are two different installation methods for installing SysInfo. Please choose one of the following:
Binary (precompiled) distributions. Everything you need is precompiled and ready to install. This is the fastest and easiest means of installing SysInfo. We strongly recommend this method as option 2 can take significant time and is difficult to get right.
Source distributions. Full source code is provided to build your own executable version. This method usually requires much more time and attention to detail to get things like C compiler software and versions right. It offers slightly more control over runtime configuration. This installation method is only recommended for advanced system administrators.
With binary distributions, everything you need is precompiled and ready to install. This is the fastest and easiest means of installing SysInfo. We strongly recommend nearly all customers install our binary distributions as this will save you significant time. There is very little difference in the installed product between installing from a binary distribution and our source distribution.
Have your license file ready if you are installing a permanent license now. See the License Requirements section for more information.
Make sure you read the Release Notes before proceeding. This file contains valuable information on what system platforms are supported.
Choose the product distribution file you wish to download. The available product distributions for download are as follows:
| Product Distribution File | Contents |
|---|---|
| mcsysinfo-5.0-os-arch.sh | Standard end-user runtime with CLI, GUI, agent. You likely just want this distribution file. |
| mcsysinfo-5.0-os-arch-noui.sh | This distribution does not include the CLI or GUI, but does include everything you need to output mcsysinforeport(5) data. This product file is intended for our OEM customers. |
| mcsysinfo-5.0-os-arch-sdk.sh | This distribution contains the C Software Developers Kit for this release. It should be installed on top of the Standard end-user runtime product as it only contains the SDK and not the required base environment. |
Follow the instructions to Download the product distribution file you choose in the previous step.
You should have a file named mcsysinfo-5.0-os-arch.sh e.g. For a SunOS/Solaris SPARC distribution, the file would be called mcsysinfo-5.0-sunos-sparc.sh
Become user `root' by running su or logging in as `root'.
su
If you are installing into a directory where SysInfo is already installed, you will need to uninstall the existing version or install SysInfo into a different directory. To uninstall the existing SysInfo, see the Remove Installation (UnInstall) section.
Unpack the distribution and start the interactive setup program which will prompt you to enter all required information:
/bin/sh mcsysinfo-5.0-os-arch.sh
The installation is now complete. Open a shell prompt. If you are using csh(1) or tcsh(1) you will need to run:
rehashTo run SysInfo, run:
mcsysinfoIf you installed SysInfo in a directory not in your $PATH then you'll need to specify the full pathname. i.e.
/opt/sysinfo/bin/mcsysinfo
Each binary distribution archive (the file you download which ends in .sh) is a self-contained self-extracting script. The top part of this file contains a sh(1) script which automatically unpacks the distribution files which are stored as a compressed (usually with bzip2(1)) tar(1) (using GNU tar) image in the bottom part of the archive file. The distribution archive contains within itself the compression tool and GNU tar programs necessary to extract the distribution. You therefor do not need your own copy of GNU tar or bzip2(1).
One of the distribution files is a program called setup which is used to actually install and configure SysInfo. When the distribution archive is run, it extracts the distribution files and executes setup unless certain command line options are used.
Follow the instructions to Download the appropriate binary distribution for your system. You should have a file named mcsysinfo-5.0-os-arch.sh e.g. For a SunOS SPARC distribution, the file would be called mcsysinfo-5.0-sunos-sparc.sh
Become user `root' by running su or logging in as `root'.
su
To see a list of available options which are supported by the self-extracting archive, run the following:
/bin/sh mcsysinfo-5.0-os-arch.sh --help
To see a list of available options which are supported by the SysInfo setup program, run the following:
/bin/sh mcsysinfo-5.0-os-arch.sh -- --helpNote the first -- option which tells the archive to pass all remaining arguments to the setup program.
To extract the distribution into the directory /tmp/mcsysinfo run the following:
/bin/sh mcsysinfo-5.0-os-arch.sh --extract --target /tmp/mcsysinfo
If you wish to perform a non-interactive installation which will not prompt for any information, run the following:
/bin/sh mcsysinfo-5.0-os-arch.sh -- --confirm --acceptlicense --installdir dirwhere dir is the name of the directory where you want to install into. You may also want to use the --override option which will override any detected error conditions which would otherwise result in being prompted for a response.
You can also specify which packages to install using --packages name1,name2,... where nameX is the name of a package. i.e. --packages base,config specifies the base and config packages. To obtain the list of valid package names, run the installation in interactive mode.
Full source code is provided to allow you to build your own executable version if you so choose. This method usually requires much more time and attention to detail to get things like C compiler software and versions right. It offers slightly more control over runtime configuration. This installation method is only recommended for advanced system administrators. We highly recommend that most customers install the binary distribution. It's much faster and easier.
Have your license file ready if you are installing a permanent license now. See the License Requirements section for more information.
Make sure you read the Release Notes before proceeding. This file contains valuable information on what system platforms are supported.
Make sure you have a supported C compiler. SysInfo usually, but not always, supports GNU's GCC compiler. However, GCC does not always provide full support for SysInfo features. This is especially true on systems running Solaris 7 and later in 64-bit mode. Please read the Release Notes for platform specific information.
You must use GNU make to build from source.
If you wish to build SysInfo with support for its GUI, then you will need Perl 5.005_03 or later and Perl-Tk 8.023 or later. Both of these are available from http://www.cpan.org.
GNU sed is required on versions of FreeBSD prior to 4.0.
Supported Platforms. SysInfo uses GNU autoconfigure (i.e. A "./configure" script) to configure many system parameters before compilation. However, this does not mean SysInfo will work on any system. SysInfo contains very specific support for specific platforms as specified in the Release Notes.
Compiling for different OS versions: In general,
SysInfo will run on the OS version you compiled it on and later
releases. It will not run on an OS older than the OS version it
was compiled on. There are exceptions to this, including those
mentioned below for Solaris. SysInfo defines some (cryptic) rules
for each OS which specify these what OS versions a binary runs on.
These rules are defined in config/os.rcf where
Solaris 7 and later: Starting with Solaris 7 Sun introduced 64-bit Solaris. You will need one SysInfo binary for 32-bit systems and one binary for 64-bit systems. Starting with SysInfo 5.0, you do not need one binary per Solaris version. You need two total binaries - one 32-bit and one 64-bit. Your 32-bit binary will run on 32-bit systems running the same or later version of Solaris. Similiarly your 64-bit binary will run on 64-bit systems running the same or later version of Solaris. (All Ultra machines are 64-bit). You can check which version you are running by executing /usr/bin/isainfo -k -v. If the output says 64-bit you are running a 64-bit kernel.
To build a binary of SysInfo for a system running a 64-bit kernel, you must have a compatible compiler. We recommend using Sun ONE Studio (formerly Forte, formerly WorkShop) C compiler on Sun Solaris systems. WorkShop Compiler 5.0 was the first Sun compiler to support 64-bit systems via the -xarch=v9 option. GCC version 3.2 and later supports 64-bit compiles via the -m64 option. However, MagniComp does not test with this configuration.
By default, a binary that runs on the local system will be built. You can force a build of a 64-bit binary on a 32-bit system and vice-versa. To build a 64-bit binary on a 32-bit system, set the environment variable KISA to be sparcv9. To build a 32-bit binary on a 64-bit system, set KISA to be sparcv8. i.e. For csh users:
setenv KISA sparcv9For sh/ksh users:
KISA=sparcv9
export KISA
Makefile:XXX: *.d: No such file or directory During initial compilation you may see error messages like this. The messages are perfectly normal and can be safely ignored. They are generated the first time make is run and indicate that a dependency file does not exist. It will be automatically generated by make and further such messages for the indicated file should not appear.
Obtain Perl 5.6.1 or later. Download it and unpack it into a directory srcdir/perl/src where srcdir is the directory containing the source to SysInfo. As of SysInfo 5.0, Perl is a required component. Without Perl, SysInfo CLI, GUI, and Perl APIs will not function.
If you wish to use the SysInfo GUI, download a copy of Perl-Tk and unpack it into a directory srcdir/perlmodules/Tk/src where srcdir is the directory containing the source to SysInfo. If you just want to use the SysInfo Command Line Interface (CLI), you can skip this step.
Follow the instructions to Download the source distribution. You should have a file named mcsysinfo-5.0.tar.gz
Unpack the distribution:
gzip -d mcsysinfo-5.0.tar.gz | tar -xf -
By default, configure will choose the name of the compiler which is correct for the system platform. However, if you have done things like make cc a link to gcc this may not work correctly in some cases. See the Compilation Notes for more specific details.
If you need to specify a compiler to use, then specify one now by setting the environment variable $CC to the name of the compiler to use. For csh users use:
setenv CC compiler
For sh/bash/ksh users use:
CC=compiler
export CC
where compiler is the name of the compiler to use. i.e cc or gcc.
./configure
Without any options configure will build SysInfo with an installation directory of /opt/sysinfo. If you wish to specify an installation directory, then use the --prefix=dir argument. For instance, to use /tools/sysinfo as the main directory, run:
./configure --prefix=/tools/sysinfo
Now compile and build everything by running make (make sure to use GNU make):
make
If you are installing into a directory where SysInfo is already installed, you will need to uninstall the existing version or install SysInfo into a different directory. To uninstall the existing SysInfo, run
rm -rf dirwhere dir is the directory where SysInfo is installed.
make install
mcsysinfoIf you installed SysInfo in a directory not in your $PATH then you'll need to specify the full pathname. i.e.
/tools/sysinfo/bin/mcsysinfo
Become user `root' be running su or logging in as `root'.
To perform an interactive uninstall where you will be prompted for required information, run the setup (installation) program as follows and follow the directions:
dir/setup --uninstallwhere dir is the directory where the software is installed.
If you wish to perform a non-interactive uninstall which will not prompt for any information, run the following:
| dir/setup --uninstall --confirm |
Copyright (c) 1992-2002 MagniComp This software may only be used in accordance with the license which is available as http://www.magnicomp.com/sysinfo/5.0/sysinfo-eu-license.shtml |
|