For instance, with a normal install of the benchmark depot:
[root@flight-100(el7cluster) ~]# alces gridware depot install benchmark
Installing depot: benchmark
> Initializing depot: benchmark
Initialize ... OK
[... lots of important output...]
> Finalizing import
Update ... OK
Dependencies ... OK
[root@flight-100(el7cluster) ~]# alces gridware depot info benchmark
Name
Benchmark
Summary
A collection of popular benchmarking applications and utilities
Description
A collection of popular benchmarking applications and utilities including
CPU, disk and memory testing applications.
Packages
mpi/openmpi/1.8.5
libs/atlas/3.10.2
apps/memtester/4.3.0
apps/iozone/3.420
apps/imb/4.0
apps/hpl/2.1
[root@flight-100(el7cluster) ~]# alces module load apps/memtester/4.3.0/gcc-4.8.5
apps/memtester/4.3.0/gcc-4.8.5
| -- libs/gcc/system
| * --> OK
|
OK
[root@flight-100(el7cluster) ~]# memtester
memtester version 4.3.0 (64-bit)
Copyright (C) 2001-2012 Charles Cazabon.
Licensed under the GNU General Public License version 2 (only).
pagesize is 4096
pagesizemask is 0xfffffffffffff000
need memory argument, in MB
Usage: memtester [-p physaddrbase [-d device]] <mem>[B|K|M|G] [loops]
[root@flight-100(el7cluster) ~]# alces gridware depot purge benchmark
Purging depot: benchmark
Purge operation will remove the following files/directories:
/opt/gridware/depots/9a1584e5
/opt/gridware/benchmark
Proceed (Y/N)? y
> Disabling depot: benchmark
Disable ... OK
> Removing depot
Purge ... OK
But then if you Ctrl-C while the depot is being installed:
For instance, with a normal install of the
benchmark
depot:But then if you Ctrl-C while the depot is being installed:
Note that
alces gridware depot install
says it already exists, but thenalces module load
cannot find a constituent package of the depot.