The variable PATH has a very special meaning to the SHELL, never set it to some random string. It needs to the a colon separated list of the utilities that will be used in your script. Normally, it should be set in your login shell initialization scripts and not messed with much after that.
With what you currently have, you are trying to execute a (probably non-existent) directory with the command:
which expands to the command:
invoked with the arguments ./sas.server and start.
I would guess that you want something more like:
This User Gave Thanks to Don Cragun For This Post:
I have a ksh script that does a bunch of things, then runs
telnet server_b
I then manually login, manually run one command (which launches an application with display back to my workstation), then logout at which point the main script takes back over, runs something else, then ends.
Is... (4 Replies)
i have a small problem getting a batxh shell script to run in shell
this is the code
the problem seems to be centered around the ffmpeg command, something maybe to do with the ' ' wrapping around the vhook part command
this is a strange problem , if i take the ffmpeg command and... (1 Reply)
Hi I am working in a java application. I need to execute a perl script(linux) which is in remote machine in java application from local machine(windows). I need to do this process automatically that is without manual intereption. Now I will explain the process clearly, at present to run the... (1 Reply)
Hello,
I have a requirement to shut down and start up my application on different environments (Dev, QA and Prod).
I have around 24 servers. I have to login to each server manually for shutinng down the application.
I wrote a shell command on each server and I am invoking those shell... (2 Replies)
Hi All,
I have a scenario :
1. A list of servers naming server21, server 22, server 23 etc. This list of servers is separate for my environments.
Env1 has 3 server
Env2 has 5 serves
Env3 has 10 servers
2. Each server accesses application through which I want to invoke some method. So... (7 Replies)
Hi Friends,
We have a application "getstatus" which needs to run on application prompt.
But it is not working with shell script.
Example:
Unix Root Prompt#
execute "crp" to go to application prompt
CRP>getstatus
displays output of app health
CRP>exit
Unix Root Prompt#
Script , which... (2 Replies)
friends,
i have application commands to execute in shell script it is something like this. i will login with user data it takes me to $ prompt. Example given below
login: data
ps : xxxx
$ MNSinput --this takes me to greater than prompt >
> ops --this is command i enter this output... (7 Replies)
Hi,
I am trying to bring down the application gracefully before bringing down AIX OS/LPAR using RC directories.
Issue: Application script is not working properly during/before AIX OS/LPAR shutdown. looks like "rc.d" directories doesn't recognize Kill script.
But Startup script (using... (0 Replies)
Linux System having all Perl, Python, PHP (and Ruby) installed
From a Shell script, can call a Perl, Python, PHP (or Ruby ?) file
eg
eg
a Shell script run in a case statement call to run a php file, also Perl or/and Python file???
Like
#!/usr/bin/bash
....
....
case $INPUT_STRING... (1 Reply)
Discussion started by: hoyanet
1 Replies
LEARN ABOUT DEBIAN
buildapp
BUILDAPP(1) User Commands BUILDAPP(1)NAME
buildapp - application to create common lisp images
SYNOPSIS
buildapp --output OUTPUT-FILE [--flag1 value1 ...]
DESCRIPTION
Required flags:
--output OUTPUT-FILE
Use OUTPUT-FILE as the name of the executable to create
Entry-point flags:
--entry NAME
Use the function identified by NAME as the executable's toplevel function. Called with SB-EXT:*POSIX-ARGV* as its only argument. If
NAME has a colon, it is treated as a package separator, otherwise CL-USER is the implied package.
--dispatched-entry DNAME
Specify one possible entry function, depending on the name of the file that is used to start the application. The syntax of DNAME is
APPLICATION-NAME/ENTRY-NAME. If the name used to start the executable matches APPLICATION-NAME, use ENTRY-NAME as the entry point.
This can be used to choose one of many possible entry points by e.g. symlinking names to the application executable. If APPLICA-
TION-NAME is empty, the specified ENTRY-NAME is used as a default if no other application names match. There may be any number of
dispatched entry points, but only one default.
Action flags:
--load FILE
Load FILE. CL:*PACKAGE* is bound to the CL-USER package before loading
--load-system NAME
Load an ASDF system identified by NAME
--require NAME
Use CL:REQUIRE to load NAME
--eval CODE
Use CL:EVAL to evaulate CODE. The code is read with CL:READ-FROM-STRING in the CL-USER package
There may be any number of load/load-system/require/eval flags. Each is executed in command-line order before creating an executable.
Load path flags:
--load-path DIRECTORY
When handling a --load, search DIRECTORY for files to load
--asdf-path DIRECTORY
When handling a --load-system, search DIRECTORY for ASDF system files to load
--asdf-tree DIRECTORY
When handling a --load-system, search DIRECTORY and all its subdirectories for ASDF system files to load
There may be any number of load-path/asdf-path/asdf-tree flags. asdf-path arguments take precedence over asdf-tree arguments.
Other flags:
--help Show this usage message
--logfile FILE
Log compilation and load output to FILE
--sbcl PATH-TO-SBCL
Use PATH-TO-SBCL instead of the sbcl program found in your PATH environment variable
For the latest documentation, see http://www.xach.com/lisp/buildapp/
buildapp 1.1 July 2010 BUILDAPP(1)