Sponsored Content
UNIX Standards and Benchmarks UNIX & LINUX Benchmarks (Version 3.11) Linux Benchmarks Filesystem Benchmarks for HDDs and SSDs Post 303045050 by RavinderSingh13 on Wednesday 11th of March 2020 07:03:46 AM
Old 03-11-2020
Thanks a TON stomp for sharing this, please keep it up Smilie

Thanks,
R. Singh
 

6 More Discussions You Might Find Interesting

1. UNIX Benchmarks

Instructions for UNIX Benchmarks

STEP 1: Get the source here: https://www.unix.com/source/bm.zip or https://www.unix.com/source/unix_linux_bench.tar.gz STEP 2: Unzip or Untar STEP 3: make STEP 4: Run STEP: 5: Please login to www.unix.com and post test results along with platform info to: Include (if you... (0 Replies)
Discussion started by: Neo
0 Replies

2. HP-UX

hdds physically

Hi, I've a HP-UX 10x running on HP9000 box and also I have 3 scsi hdd(9Gb), one of them is working. I need to check the other 2 hdd physically. Is there an utility to check them from unix or another way to do it? Thanks.... (5 Replies)
Discussion started by: efrenba
5 Replies

3. UNIX for Dummies Questions & Answers

hwo to find shared filesystem and local filesystem in AIX

Hi, I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local. Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies

4. Shell Programming and Scripting

Understanding Benchmarks

I need a little clarification in understanding why there would be a need for a benchmark file when used with a backup script. Logically thinking would tell me that the backups itself(backuptest.tgz) would have the time created and etc. So what would be the purpose of such a file: touch... (6 Replies)
Discussion started by: metallica1973
6 Replies

5. Solaris

SPARC T4-1/Solaris 11/Add 2 new HDDs in RAID 0 configuration

Hi, Couple of sentences for background: I'm a software developer, whose task was to create a server software for our customer. Software is ready for deployment and customer has a new T4-1 SPARC, but somehow it also became my task also to setup the server. I have managed to get the server is up... (13 Replies)
Discussion started by: julumme
13 Replies

6. AIX

IBM AIX 5.2 cloning Hdds

I have an old IBM Power 5 9111-520 that has data on it but the system is failing. I need to move it to a more reliable server. The current system has two drives and no raid. I would like to setup my "newer" system with raid and two partitions then clone my setup over. What is the best way to do... (2 Replies)
Discussion started by: BDC80
2 Replies
GIMPTOOL(1)							 GIMP Manual Pages						       GIMPTOOL(1)

NAME
gimptool - perform various Gimpy functions SYNOPSIS
gimptool [--prefix[=DIR]] [--exec-prefix[=DIR]] [--version] [--help] [--quiet] [--silent] [-n] [--just-print] [--dry-run] [--recon] [--bindir] [--sbindir] [--libexecdir] [--datadir] [--sysconfdir] [--sharedstatedir] [--localstatedir] [--libdir] [--infodir] [--mandir] [--includedir] [--gimpplugindir] [--gimpdatadir] [--libs] [--libs-noui] [--cflags] [--cflags-noi] [--build plug-in.c] [--build-strip plug-in.c] [--install plug-in.c] [--install-strip plug-in.c] [--install-admin plug-in.c] [--install-bin plug-in] [--install-admin-strip plug-in.c] [--install-bin-strip plug-in] [--install-admin-bin plug-in] [--install-script script.scm] [--install-admin-script script.scm] [--uninstall-bin plug-in] [--uninstall-admin-bin plug-in] [--uninstall-script script.scm] [--uninstall-admin-script script.scm] DESCRIPTION
gimptool is a tool that can, among other things, build plug-ins or scripts and install them if they are distributed in one source file. gimptool can also be used by programs that need to know what libraries and include-paths Gimp was compiled with. This is especially useful in Makefiles. On Unix, gimptool is a script. On Windows, it is a program. They should be more or less compatible. This manual page describes the Unix script version. OPTIONS
gimptool accepts the following options: --version Print the currently installed version of Gimp on the standard output. --help Print out the help blurb, showing commonly used commandline options. --quiet Run quietly without echoing any of the build commands. --silent Run silently without echoing any of the build commands. Same as --quiet. -n Test mode. Print the commands but dont actually execute them. Useful for making dry runs for testing. --just-print Test mode. Print the commands but dont actually execute them. Same as -n. --dry-run Test mode. Print the commands but dont actually execute them. Same as -n. --recon Test mode. Print the commands but dont actually execute them. Same as -n. --bindir Outputs the bindir used to install the Gimp. --sbindir Outputs the sbindir used to install the Gimp. --libexecdir Outputs the libexecdir used to install the Gimp. --datadir Outputs the datadir used to install the Gimp. --sysconfdir Outputs the sysconfdir used to install the Gimp. --sharedstatedir Outputs the sharedstatedir used to install the Gimp. --localstatedir Outputs the localstatedir used to install the Gimp. --libdir Outputs the libdir used to install the Gimp. --infodir Outputs the infodir used to install the Gimp. --mandir Outputs the mandir used to install the Gimp. --includedir Outputs the includedir used to install the Gimp. --gimpdatadir Outputs the actual directory where the Gimp data files were installed. --gimpplugindir Outputs the actual directory where the Gimp plugins were installed. --build plug-in.c Compile and link plug-in.c into a Gimp plug-in. --build-strip plug-in.c Compile,link, and strip plug-in.c into a Gimp plug-in. --install plug-in.c Compile, link, and install plug-in.c into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-strip plug-in.c Compile, link,strip, and install plug-in.c into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin plug-in.c Compile, link, and install plug-in.c into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-bin plug-in Install plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin-bin plug-in Install plug-in into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-bin-strip plug-in Install stripped plug-in into the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --install-admin-bin-strip plug-in Install stripped plug-in into the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --install-script script.scm Install script.scm into the user's personal Gimp script directory ($HOME/.gimp-1.2/scripts) --install-admin-script script.scm Install script.scm into the system-wide Gimp script directory (/usr/share/gimp/1.2/scripts) --uninstall-bin plug-in Uninstall plug-in from the user's personal Gimp plug-in directory ($HOME/.gimp-1.2/plug-ins) --uninstall-admin-bin plug-in Uninstall plug-in from the system-wide Gimp plug-in directory (/usr/lib/gimp/1.2/plug-ins) --uninstall-script script.scm Uninstall script.scm from the user's personal Gimp script directory ($HOME/.gimp-1.2/scripts) --uninstall-admin-script script.scm Uninstall script.scm from the system-wide Gimp script directory (/usr/share/gimp/1.2/scripts) --libs Print the linker flags that are necessary to link a Gimp plug-in. --libs-noui Print the linker flags that are necessary to link a Gimp plug-in, for plugins that do not require the GTK libs. --cflags Print the compiler flags that are necessary to compile a Gimp plug-in. --clags-noui Print the compiler flags that are necessary to compile a Gimp plug-in for plugins that do not require the GTK libs. --prefix=PREFIX If specified, use PREFIX instead of the installation prefix that Gimp was built with when computing the output for the --cflags and --libs options. This option is also used for the exec prefix if --exec-prefix was not specified. This option must be specified before any --libs or --cflags options. --exec-prefix=PREFIX If specified, use PREFIX instead of the installation exec prefix that Gimp was built with when computing the output for the --cflags and --libs options. This option must be specified before any --libs or --cflags options. ENVIRONMENT
GTK_CONFIG to get the location of the gtk-config program. CC to get the name of the desired C compiler. CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. DESTDIR to add a prefix to the install/uninstall path. LDFLAGS to get the prefered flags for passing to the linker. LIBS for passing extra libs that may be needed in the build process. For example, LIBS=-lintl . GTK_CONFIG path to the gtk-config shell script used by gimptool and in the build process of many gtk apps. SEE ALSO
gimp(1), gimprc(5), gimp-remote(1), gtk-config(1) AUTHORS
gimptool was written by Manish Singh (yosh@gimp.org) and based on gtk-config by Owen Taylor (owen@gtk.org). This man page was written by Ben Gertzfield (che@debian.org), and tweaked by Manish Singh (yosh@gimp.org), Adrian Likins (adrian@gimp.org) and Marc Lehmann (pcg@goof.com>). COPYRIGHT
Copyright (C) 1998 Owen Taylor and Manish Singh Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, pro- vided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in sup- porting documentation. Version 1.2.3 26 June 2001 GIMPTOOL(1)

Featured Tech Videos

All times are GMT -4. The time now is 05:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy