Sponsored Content
Special Forums UNIX and Linux Applications High Performance Computing How to check performance of your HPC cluster? Post 302643311 by otheus on Saturday 19th of May 2012 03:49:51 AM
Old 05-19-2012
the standard measuring tool is HPL which solves for a very large multidimensional array. Prepackaged rpms might be found in the Rocks distribution. The answer is yes to each of your other questions
This User Gave Thanks to otheus For This Post:
 

8 More Discussions You Might Find Interesting

1. Solaris

Performance check without a counterpart

Hi, is it possible to check out the speed limits of a box without a remote peer for netio and stuff? I transferred 1 Terrabyte last night, which is not really much and need to find the bottleneck. The remote server is soon going to retire, yet I need to copy the 8T to the new machine. This... (9 Replies)
Discussion started by: PatrickBaer
9 Replies

2. Shell Programming and Scripting

how to check all the applications are in cluster using shell script

Hi I have an application running in four different node.The server is tomcat.Each node in each tomcat server.How do i check whether all the nodes are in cluster using shell script. any command to check this would be of great use.:) (2 Replies)
Discussion started by: ahamed
2 Replies

3. Shell Programming and Scripting

Monitoring script to check if cm cluster is up or not.

hi guys have this little problem, need some help from script gurus. basically I'm running hpux cmviewcl command, cmviewcl command will produce db1pkg up running enabled box1 my script PSV='box1' STAT='up' check_db1pkg() { # assign cmviewcl output... (2 Replies)
Discussion started by: sparcguy
2 Replies

4. UNIX for Dummies Questions & Answers

How to check if the server is on a Cluster

Hi im connecting to a datacenter remotely. is there a command to know if the server is on a cluster? i want to know the command to use in these OS(hp-ux,solaris,linux) Thanks (6 Replies)
Discussion started by: jinslick25
6 Replies

5. Linux

Cluster check

I am working on a Linux server and want to check the cluster status. I dont know how many server is in cluster and what is the command to check. could you please help me to get the cluster status? (4 Replies)
Discussion started by: anshu ranjan
4 Replies

6. AIX

How to check if a filesystem is part of a cluster

Hello, - How do I know if a filesystem is part of a cluster? - Or do I have to check if the vg related to the fs is part of a cluster instead? if so, how do I check it? - I would also need to check if there are vxfs type inside aix machines and if there are, how do I know if that type of... (2 Replies)
Discussion started by: asanchez
2 Replies

7. Red Hat

How to check performance?

Hi, all What would be the a,b,c in troubleshooting slow performance on RH box, I type and it became really slow, what commands or log files to examine. What parameters to check? Thanks all T (2 Replies)
Discussion started by: trento17
2 Replies

8. Solaris

System Check Performance Tuning

Hello Forum, Well I am fairly new to this Solaris os thing. One thing I would like to check for system health and performance. I know the codes like prstat,vmstat,sar,iostat,netstat,prtdiag -v, What else does a want to be sys admin have to look for when checking a solaris box? I know... (3 Replies)
Discussion started by: br1an
3 Replies
build(1)                                                      General Commands Manual                                                     build(1)

NAME
build - build SuSE Linux RPMs in a chroot environment SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm] build --help build --verify DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc- tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec file for example), even if the package does not use BuildRoot. build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec- tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be sufficient for the build. If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current directory. OPTIONS
--clean remove the build system and reinitialize it from scratch. --no-init skip the build system initialization and start with build immediately. --list-state list rpms that would be used to create a fresh build root. Does not create the build root or perform a build. --rpms path1:path2:path3... Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari- able. --arch arch1:arch2:arch3... What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify this option. --root buildroot Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable. --useusedforbuild Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the same packages used for the srcrpm build. --norootforbuild --help Print a short help text. --verify verify the files in an existing build system. .spec FILE OPTIONS The build command interprets some special control comments in the specfile: # norootforbuild # needsrootforbuild build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2, the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec- tively. # needsbinariesforbuild provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root. ENVIRONMENT
BUILD_ROOT The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default. BUILD_RPMS Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value which will do the trick if you have the SuSE Linux DVD mounted. BUILD_RPM_BUILD_STAGE The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip- tions. "-ba" is the default. You can use this to add more options to RPM. SEE ALSO
rpm(1), Maximum RPM: http://www.rpm.org/max-rpm/ cross distribution packaging: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to SUSE packaging standards and guidelines: http://en.opensuse.org/Packaging (c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
All times are GMT -4. The time now is 04:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy