Sponsored Content
Top Forums Shell Programming and Scripting Help with oracle11i apps concurrent manager request error message Post 302093723 by Ygor on Monday 23rd of October 2006 05:03:33 AM
Old 10-23-2006
For a script to be run by the concurrent manager, you need to have two executable files in your application bin directory:
1. the script itself, with a .prog extension, e.g. XZY.prog
2. a symbolic link to fndcpesr with the same name as the script, e.g. XZY

When defining the concurrent executable, use the name of the script without the .prog extension.
 

6 More Discussions You Might Find Interesting

1. Red Hat

error on virtual manager

In red hat linux server 6 I start up virtual manager and I get below error prompt. Package reuired for KVM usage The following packages are not installed qemu-kvm These are required to create KVM guests locally. Would you like to install them now . I press yes but the package cannot... (0 Replies)
Discussion started by: chuikingman
0 Replies

2. Linux

Lpstat: Bad Request Error in Linux

Dear Team, Earlier my lpstat syntax is working on o/s, I have installed cups "cups-1.6.1" after that I'm not able to open the printer option in GUI and cannot do the query "lpstat -a" Below is the error i'm getting..Request you to advice me the best to me. # lpstat lpstat: Bad Request ... (3 Replies)
Discussion started by: Mohammed Faiz
3 Replies

3. AIX

Difference between concurrent and enhanced concurrent VG

Hi, What are the differences between concurrent and enhanced concurrent VGs.? Any advantages of enhanced concurrent VG over normal concurrent vg Regards, Siva (2 Replies)
Discussion started by: ksgnathan
2 Replies

4. Web Development

Error on executing soap request using Curl command

hi, i have curl command to POST a soap request to web service. I have a file (query.xml) which has all the soap message attached to it I just don't seem to be able to properly post it. curl command curl -s -H "Content-Type: text/soap+xml;charset=UTF-8" -H "SOAPAction:" -d @query.xml... (2 Replies)
Discussion started by: siramitsharma
2 Replies

5. Ubuntu

Unable to connect only when using wget with 400 bad request error

Hi I have a proxy configured on my ubuntu o.s. running on vmware player, but when trying to wgetDownload Nagios Core from SourceForge.net, I have the following error: failed: Connection refused I have check on the web, they ask me to run sudo ufw status, but the output is enabled, so what... (0 Replies)
Discussion started by: fretagi
0 Replies

6. SCO

Lp ERROR when printing by request-id

Running SCO 5.0.7 and when users besides root or lp execute lp -i request-id -H resume for held print requests an error "You aren't allowed to do that" to fix "You must be logged in as lp or root" is received. Users can execute lp (without these options) along with lpstat without errors. This is... (2 Replies)
Discussion started by: powwm
2 Replies
tryto(1)						      General Commands Manual							  tryto(1)

NAME
tryto - tries to run a command limited by a timeout or number of tries, can be used to run as svlogd(8) processor. SYNOPSIS
tryto [-pPv] [-t sec] [-k ksec] [-n tries] prog DESCRIPTION
prog consist of one or more arguments. tryto runs and watches prog, feeding its standard input to prog's standard input. If prog exits with a return code other then 0, tryto runs prog again after sleeping one second. If the number of retries reaches the maximal number of tries, tryto prints an error message and gives up. If the timeout sec seconds is reached and prog is still running, tryto sends a TERM signal to prog, waits ksec seconds for prog to termi- nate, then sends a KILL signal if prog still is there, and exits as soon as possible. OPTIONS
-t sec timeout. Set the timeout to send TERM to prog to sec seconds. Default is 180. -k ksec kill timeout. Set the timeout to send KILL to prog to ksec seconds. Default is 5. -n tries Set the maximal number of tries to tries. If prog exited with a return code other that 0, tryto tries to rewind standard input to the beginning using lseek(2) before starting prog again. Default is 5. -p processor. Use this option if you run tryto as a svlogd(8) processor (see below). -P process group. Run prog in a new session and process group, and send signals on timeout to prog's process group instead of its pid. -v verbose. Print verbose messages to standard error. PROCESSOR
If tryto sees the -p option, tryto runs as a svlogd(8) or multilog(8) processor, making use of filedescriptors 4 and 5: Before starting prog, tryto moves the filedescriptor 5 to 2, so all error messages from tryto and prog will be saved in svlogd(8)'s state to be processed on the next run of tryto -p. After starting prog, tryto first feeds all data it reads from filedescriptor 4 into prog's standard input, then all data from filedescrip- tor 0. If prog fails by timeout sec seconds or maximal number of tries, tryto prints all data from standard input to standard output, an error message to standard error, and exits with 0. EXIT CODES
If tryto itself fails, it returns 111. If tryto runs as a svlogd(8) processor, tryto returns 0 in all other cases. If prog was run successfully, tryto returns 0. If prog failed by timeout, tryto returns 100. If prog failed by maximal number of tries, tryto returns the last return code from prog. SEE ALSO
socklog(8), uncat(1), svlogd(8), multilog(8), lseek(2) http://smarden.org/socklog/ http://smarden.org/runit/ AUTHOR
Gerrit Pape <pape@smarden.org> tryto(1)
All times are GMT -4. The time now is 01:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy