Downloads

Please refer to the FAQ and the known limitations when you run into problems.

Several people and companies contributed to SCC. Usage of these contributions to SCC is on your own risk. They give no warranty and are not responsible for problems caused by the modifications/extensions. Please test new releases of scc and scc-srv before deploying the software on your production systems.

As the download of scc-win contains software from putty, we copy the following warning:
"LEGAL WARNING: Use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is outlawed. If in doubt, you should seek legal advice before downloading it. You may find this site useful (it's a survey of cryptography laws in many countries), but I can't vouch for its correctness."

MD5 sums of the downloads are available here. All packages/depots/rpms use the same code base. Refer to the FAQ for the availability of SCC on other platforms. The following releases and downloads are available:

The project is registered at Sourceforge. Access the repository here. Use the trunk directories of scc, scc-srv and scc-win for the latest and greatest of the sub projects.

RPM

The software has been tested on CentOS5. Install release 1.17.23-1 of scc and release 1.11.18-1 of scc-srv with the following commands:

	rpm -U ./scc-1.17.23-1.noarch.rpm
	rpm -U ./scc-srv-1.11.18-1.noarch.rpm

When rpm complains that the package "is for a different operating system", you have to add the --ignoreos option to the command line.

Note that scc is run during the postinstall phase. In that phase, rpm cannot produce any data. This means that the snapshot does not contain any rpm data after a fresh install. This data is collected during the next (manual or scheduled) run of scc.

Packages on Debian

Previous versions of the software have been tested on Debian 4.0 (and Damn Small Linux 3.3). Install release 1.17.23-1 of scc and release 1.11.18-1 of scc-srv with the following commands:

	dpkg -i ./scc_1.17.23-1_all.deb
	dpkg -i ./scc-srv_1.11.18-1_all.deb

Depending on the configuration, dpkg can ask for confirmation to use the old or the new configuration files. As the only configuration files for scc reside in the newconfig directory and have to be activated manually, use the --force-confnew option to keep them up-to-date.

On our Debian VM, the command hwinfo (version 13.11) produces some data concerning parport and pnp via syslog on the terminal. This data is not part of the snapshot and when scc runs via cron, it is recorded in /var/log/messages.

Packages on Slackware

Note: the package software of Slackware does not provide a preinstall script. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook.

The software has been tested on Slackware 11. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	installpkg scc-1.17.23-noarch-1.tgz
	installpkg scc-srv-1.11.18-noarch-1.tgz

To upgrade existing installations of scc and scc-srv, use the following commands:

	/opt/scc/bin/scc		# catch last changes 
	upgradepkg scc-1.17.23-noarch-1.tgz
	upgradepkg scc-srv-1.11.18-noarch-1.tgz

After removing scc or scc-srv, the data directories remain on the system and have to be removed manually.

Packages (pacman and pacman-g2)

Install or upgrade to release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pacman -U ./scc-1.17.23-1.pkg.tar.gz
	pacman -U ./scc-srv-1.11.18-1.pkg.tar.gz

Use the --noarch option for pacman-g2 (Frugalware).

Pisi packages on Pardus

Install or upgrade to release 1.17.23-1 of scc and release 1.11.18-1 of scc-srv with the following commands:

	pisi install ./scc-1.17-23.pisi
	pisi install ./scc-srv-1.11-18.pisi

The software has been successfully installed on Pardus2008, on Pardus2007 pisi failed. To install SCC on Pardus2007, use the source install of SCC. On early versions of Pardus2009 the --reinstall option has to be used to upgrade SCC.

Packages on FreeBSD

Previous versions of the software have been tested on FreeBSD 6.2. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pkg_add ./scc-1.17.23.FreeBSD.tgz
	pkg_add ./scc-srv-1.11.18.FreeBSD.tgz

Remove the previously installed version of the software when upgrading. To upgrade scc from 1.5.37 to 1.17.23, use the following command:

	pkg_delete scc-1.5.37
	pkg_add ./scc-1.17.23.FreeBSD.tgz

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc.

Packages on DragonFlyBSD

Previous versions of the software have been tested on DragonFlyBSD 1.10.1. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pkg_add ./scc-1.17.23.DragonFlyBSD.tgz
	pkg_add ./scc-srv-1.11.18.DragonFlyBSD.tgz

Use the -u option to upgrade an already installed version of the software. When you remove the scc-client, it runs one more time to collect data. This has to be done as the removal is also part of a regular upgrade. After the deinstall, the installation directory is removed. The data and configuration directories are still present.

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc.

Do not leave any additional files in the /opt/scc and /opt/scc-srv hierarchies during an upgrade or pkg_add will complain that it could not remove the directory.

Note that the software has been build for DragonFlyBSD 1.10.1 on an i386 architecture. Installing it on other versions of DragonFlyBSD will succeed, but pkg_add will complain about the different OS version. When pkg_add refuses to install the software, use the -f option to force the install or download the source and generate the DragonFlyBSD packages with the scripts: dragonflybsd-gen-scc and dragonflybsd-gen-scc-srv.

Packages on NetBSD

Previous versions of the software have been tested on NetBSD3.1. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pkg_add ./scc-1.17.23.NetBSD.tgz
	pkg_add ./scc-srv-1.11.18.NetBSD.tgz

Use the -u option to upgrade an already installed version of the software. When you remove the scc-client, it runs one more time to collect data. This has to be done as the removal is also part of a regular upgrade. After the deinstall, the installation directory is removed. The data and configuration directories are still present.

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc.

Do not leave any additional files in the /opt/scc and /opt/scc-srv hierarchies during an upgrade or pkg_add will complain that it could not remove the directory.

The software has been build for NetBSD 3.1. Installing it on other versions of NetBSD will succeed, but pkg_add will complain about the different OS version. To avoid this, you can download the source and generate the NetBSD packages with the scripts: netbsd-gen-scc and netbsd-gen-scc-srv.

Packages on OpenBSD

Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pkg_add -B / ./scc-1.17.23-OpenBSD.tgz
	pkg_add -B / ./scc-srv-1.11.18-OpenBSD.tgz

Remove the previously installed version of the software when upgrading. To upgrade scc from 1.5.37 to 1.17.23, use the following command:

	pkg_delete -B / scc-1.5.37-OpenBSD
	pkg_add -B / ./scc-1.17.23.OpenBSD.tgz

Note that scc is run during the postinstall phase. In that phase, pkg_info cannot produce any data. This means that the snapshot does not contain any pkg_info data after a fresh install. This data is collected during the next (manual or scheduled) run of scc.

PET packages on PuppyLinux

Note: the package software of PuppyLinux does not provide a preinstall script. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook. The warning from the client postinstall script about the missing lockfile can be ignored.

Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	petget $(pwd)/scc-1.17.23.pet
	petget $(pwd)/scc-srv-1.11.18.pet

pacman on ttylinux

Note: the package software of ttylinux does not provide a preinstall script. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook. The warning from the client postinstall script about the missing lockfile can be ignored.

The packages are built for ttylinux 11.1. Pacman checks for the architecture in the name of the package. SCC consists of scripts only and can run on any architecture. Rename the package to your architecture and install. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pacman --install ./scc-1.17.23-i486.tbz
	pacman --install ./scc-srv-1.11.18-i486.tbz

Before upgrading scc, the previous version should be run and removed with the -e option.

Note that diff and sort are implemented by busybox after a default system install. As scc requires these programs to produce the logbook and the html-format of the data, the logbook and the html-files are empty. Transferring these files to a fully functional scc-srv will produce the logbook and the html-files on the system running scc-srv.
On default installs of ttylinux the scc-srv software will not function. The package is added for those who install the required additional software: apache, sort and diff.

Packages on Slitaz

Both scc and scc-srv packages in slitaz format depend upon diff-utils and coreutils-file-sort to replace the limited busybox functionality for diff and sort. Install or upgrade to release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	tazpkg install ./scc-1.17.23.tazpkg
	tazpkg install ./scc-srv-1.11.18.tazpkg

Installp packages on AIX

The installp packages are provided by Eduardo Alvarenga and they are produced on AIX 5.3. To generate these packages, you require /usr/sbin/mkinstallp from bos.adt.insttools. To install or upgrade to release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	installp -a -d ./scc.1.17.23.1.bff scc
	installp -a -d ./scc-srv.1.11.18.1.bff scc-srv

SD-UX depots on HP-UX

The software depots are provided by Eduardo Alvarenga. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	swinstall -s $(pwd)/scc-1.17.23.hpux.depot scc
	swinstall -s $(pwd)/scc-srv-1.11.18.hpux.depot scc-srv

To register both depots, use the commands:

	swreg -l depot $(pwd)/scc-1.17.23.hpux.depot
	swreg -l depot $(pwd)/scc-srv-1.11.18.hpux.depot

To copy both products to an existing depot, use the commands:

	swcopy -s $(pwd)/scc-1.17.23.hpux.depot scc @ /your/depot
	swcopy -s $(pwd)/scc-srv-1.11.18.hpux.depot scc-srv @ /your/depot

Packages on Solaris

Both scc and scc-srv require the XPG4 software (SUNWxcu4) on the system to work correctly. The packages can be installed on sparc and intel architectures. The software has been tested on Solaris 6, 8, 9 and 10. Install release 1.17.23 of scc and release 1.11.18 of scc-srv with the following commands:

	pkgadd -d ./scc-1.17.23.sunos.pkg -a none scc
	pkgadd -d ./scc-srv-1.11.18.sunos.pkg -a none scc-srv

During the installation, you will be asked whether the installation-scripts should run. Use the following admin-file and the -n option for pkgadd to fully automate the installation process.

	basedir=default
	mail=
	runlevel=nocheck
	conflict=nocheck
	setuid=quit
	action=nocheck
	partial=nocheck
	instance=overwrite
	idepend=nocheck
	rdepend=nocheck
	space=nocheck

Note that installs in a zone will fail for release prior to S10_73. Use pkgtrans to transfer the contents of the pkg-file to a directory structure and then install from the directory.

Source

Use this method of installation when the native install format for your OS is not available. The software has been tested on TRU64V5.1 and AIX 5.3. To install scc from source, use the following commands:

	tar zxf scc-1.17.23.src.tar.gz
	cd scc-1.17.23
	./scc-install

To install scc-srv from source, use the following commands:

	tar zxf scc-srv-1.11.18.src.tar.gz
	cd scc-srv-1.11.18
	./scc-srv-install

The tarball contains scripts to generate all depots, rpms and packages after modifying the source-files. Refer to the relocate script when you want to install the software in non-default directories. Be sure to edit this script before using it.

Windows executable

The download is a self extracting executable that was built by Ghost Installer from Ethalone.

The server-part of scc is not available for Windows, only the client-part. The client software has been tested on W2K, W2K3 and WXP. Note that you need additional software on your Windows systems. The software requires perl. We tested the software with ActivePerl from Active State.

Note: the executable does not provide a preinstall. Therefore you have to run scc manually before installing a new release. Otherwise the changes, made after the last run of scc and before the install of the new release, are not recorded in the logbook(s). At the end of the installation, scc can be run. It only collects data from the system it is installed on, not from other systems.

Note that after installing the client-software, the scheduling of scc has to be configured. You need to run scc with sufficient privileges. Running the software as domain administrator, even enables you to install the software on a single system and retrieve data from all other systems in your domain. Refer to the documentation of scc-collect for an overview of all options you can use to indicate what systems to collect data from.

Windows source

Unpack the archive to retrieve the build environment of the Windows client of SCC. You can adjust the source for example to adjust the location of the install. Use Ghost Installer from Ethalone to build the executable.

MD5 sums

Here are the size in bytes and the MD5 sums of all the downloads:

     scc_1.17.23-1_all.deb                   197666 d64c68a723f2cc36bed4ec9c17aa9200
     scc.1.17.23.1.bff                       538624 3f1d52237b501fec224677eed27b7ccf
     scc-1.17.23-1.noarch.rpm                211632 0d2df3252cbae764fa955c562583957d
     scc-1.17.23-1.pkg.tar.gz                195530 888bb109c3c33bd6819b7469797d636a
     scc-1.17.23.DragonFlyBSD.tgz            195823 96c6e09852ae7b70c248f939d8b17904
     scc-1.17.23.FreeBSD.tgz                 195573 9c09fa4f9bea04132cd74f5ab31d49d7
     scc-1.17.23.hpux.depot                  819200 12c22877bdb14e9b63b64950002ee703
     scc-1.17.23-i486.tbz                    151207 e17d8c804f3ccff7782bb3a6d1c5211a
     scc-1.17.23.NetBSD.tgz                  195814 92558931ca6e30c2d48e189b896b6cc0
     scc-1.17.23-noarch-1.tgz                193468 393f3ee6dd76542a48b36d0ceabc00ea
     scc-1.17.23-OpenBSD.tgz                 195468 f62648e44e3f5148960d8e7bb742bec3
     scc-1.17.23.pet                         195201 c9c00f34afba2237bec28c00b5e3fe84
     scc-1.17-23.pisi                        149493 5fc57eab2e0df25436219bcc945df06a
     scc-1.17.23.src.tar.gz                  211110 0eb4356492bed0fdffe31b18cdc92c48
     scc-1.17.23.sunos.pkg                   770048 327bd49f9e437850a63cff7948eb5417
     scc-1.17.23.tazpkg                      185344 eaeee64696b238637e1092e3592874ae
     scc-srv_1.11.18-1_all.deb               161126 962760ae16132ae419522cff360dcdac
     scc-srv.1.11.18.1.bff                   492544 d2bbe6a0ca139e8b138ad394bcebd8c0
     scc-srv-1.11.18-1.noarch.rpm            189051 79e1753537f862830c483224cbbcf879
     scc-srv-1.11.18-1.pkg.tar.gz            159850 129975b69ccd13a7d297ec61890d22c5
     scc-srv-1.11.18.DragonFlyBSD.tgz        161857 9686dc0c0fea7a9d67523e57f452edcb
     scc-srv-1.11.18.FreeBSD.tgz             161604 edf4f69cf389d3923d40bf172d57129f
     scc-srv-1.11.18.hpux.depot              727040 29bb5df476c539cf3bc883c4ab9400ef
     scc-srv-1.11.18-i486.tbz                101540 42664e62886d45d62714a441641eb4c5
     scc-srv-1.11.18.NetBSD.tgz              161846 b27777b75b96442cd027cd2610c615d6
     scc-srv-1.11.18-noarch-1.tgz            158008 ee8a630c01d2a46726e02a53f17127c3
     scc-srv-1.11.18-OpenBSD.tgz             161024 0bae7fff0eb1a1691b61b2e8495c4e8e
     scc-srv-1.11.18.pet                     158316 623d28ba97a40f6ecd6b16b5d6b3b1b8
     scc-srv-1.11-18.pisi                     95977 b781edccc66e85df8a4604f814a5f2fd
     scc-srv-1.11.18.src.tar.gz              178555 327721307080d76d22c17d88af4b36b0
     scc-srv-1.11.18.sunos.pkg               654848 10e0340a2841efda62c34ff82d1ec742
     scc-srv-1.11.18.tazpkg                  147968 214623a50674c06b2774be328fa272aa
     scc-win-1.5.8.exe                      1332131 5e3a525fdd7934e68a58bb1ce691fade
     scc-win-1.5.8.src.tar.gz               1330205 0598389b2412b27d583c03ee22c00de5