Sponsored Content
Full Discussion: running vendor shell scripts
Top Forums UNIX for Dummies Questions & Answers running vendor shell scripts Post 49909 by Optimus_P on Tuesday 13th of April 2004 02:07:00 PM
Old 04-13-2004
when installing software for the most part i dont read the makefiles and stuff like that.

if it is a shell script i tend to go over it to see what it is doing exactly, this serves 3 purposes.

1) i know what is going on when i run it.
2) mabey they do something i dont do so i can get a few hints for future scripts i might have to write.
3) tends to show me what kinda people i am dealing with due to sloppy codeing or if they just bang it out or is it written better then something i would have done.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Cron running shell scripts.

What are the rules of calling shell scripts in cron. How do I go about setting up the correct PATHS that calls a script, which then calls another sub script all of which has to retain the orginal PATHS and VARS that I've set up in first script Confused.. ok Well Cron calls a script... (3 Replies)
Discussion started by: cfoxwell
3 Replies

2. UNIX for Dummies Questions & Answers

Running shell scripts on a remote server

Hi - I am running Mac OS X (Terminal) at my current workstation, and I would like to telnet to my local server to run a shell script. The local server is a Solaris machine (don't know the version or the type of Unix being run on it, sorry.) The problem I have is that when I create a #!/bin/sh... (2 Replies)
Discussion started by: pepintheshort
2 Replies

3. UNIX for Advanced & Expert Users

unix shell scripts for running on solaris

am new to programmming any body suggest , how to execute, shell script interactively and like stream line edit (3 Replies)
Discussion started by: srini_ibmadmin
3 Replies

4. Shell Programming and Scripting

Running SQL Scripts from Shell script - Need insight!

I've a script that fetches various values from the database as below: #! /bin/ksh $conn="user/pwd@service_name" `sqlplus -s << $conn EOF1 @xyz.sql @pqr.sql @abc.sql EOF1` The output of the script should generate txt files containing the results from queries which are further... (6 Replies)
Discussion started by: manthasirisha
6 Replies

5. Shell Programming and Scripting

Running shell scripts from web browser

I am in need of a mechanism to run shell scripts from web browser. Could any one of you guide me as to which technology to choose? I have some scripts which take some arguments. Appreciate you response. (7 Replies)
Discussion started by: corleone
7 Replies

6. Shell Programming and Scripting

Running shell scripts automatically without using Batch or at commands

I have been trying to run a unix script which contains many sql statements.I need to run this script every monday morning. I tried to run on command prompt, it works fine. But while I run it via batch or at command., it returns with library module could not be loaded (libcompat.1.o could not be... (3 Replies)
Discussion started by: ritzwan0
3 Replies

7. Shell Programming and Scripting

Long running shell scripts shuts donw the machine!

Hi, I am very new to shell scripting. I have a script called "RunDMol3.sh" which takes a directory name as input parameter, process somthing using files in the folder and writes output files in the same folder. This is a very heavy job and takes about 1.5 hrs. When I run in manually the script... (2 Replies)
Discussion started by: ramesh.jitkar
2 Replies

8. Programming

running PLSQL scripts through shell script

I am running the following ealth checks on my server there are two databases in my server . MODEL1 and MODEL2 i connect with the first database as sqlplus model1/password Then i exceute a query select x from table (4 Replies)
Discussion started by: asalman.qazi
4 Replies

9. Shell Programming and Scripting

Automatic running of Shell scripts

Hi, I have this problem of merging 2 shell scripts and run it one after the other. For eg: script A runs to give OutputA. This OutputA should become the input of script B which will run to give OuputB. Now this has to happen automatically i.e, script A and script B should run consecutively one... (1 Reply)
Discussion started by: Vindhyaauri
1 Replies

10. Shell Programming and Scripting

Running shell scripts from command

I have written a few shellscripts to run a videogame (starcraft) at different patched versions. For example bw113 runs the 1.13 version of the game. These works perfectly when I run them from command line (./bw113). However I cannot get it to work via mouseclick. Some Information: - I have... (5 Replies)
Discussion started by: lordsloth
5 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)
All times are GMT -4. The time now is 09:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy