Sponsored Content
Top Forums Shell Programming and Scripting JBOSS process quits on shell exit Post 302688501 by Corona688 on Sunday 19th of August 2012 01:15:09 PM
Old 08-19-2012
When you close your terminal window, anything that still has open file descriptors referring to the terminal is killed. Anything you run will inherit copies of the terminal file descriptors unless they close them themselves or you close them first.

Run them with nohup to prevent them accidentally keeping around such file descriptors.

nohup commandname ...
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

exit from telnet kills orbix process

Hi, I'm using a bourne shell to kick off a 3rd Pty app. This app uses Orbix. When I exit from the telnet session which started the app or hit CTRL-C at the command line, the orbix process dies, yet all other process remain. I've tried starting the app as a background process, but it still... (1 Reply)
Discussion started by: edgarm
1 Replies

2. Shell Programming and Scripting

Shell script process remains after "exit 1"

I have a script that performs an oracle export: <snip> if then exp / full=y file=${exp_file} log=${exp_log} direct=y feedback=1000000 STATISTICS=NONE buffer=20000000 else exp / full=n owner=${schema_name} file=${exp_file} log=${exp_log} direct=y feedback=1000000... (4 Replies)
Discussion started by: Squeakygoose
4 Replies

3. Shell Programming and Scripting

way to exit a infinite process

There is a sh file called "agg.sh", this is a kind of negative scenario, this script would fail as expected, but the problem is that after executing the script the following o/p is displayed continuosly without returning the control.We have to press "crtrl+c" to exit the script. ... (3 Replies)
Discussion started by: villain41
3 Replies

4. Programming

Why does my child process not exit?

Im sure it has something to do with the wait() call, but everything ive tried either leaves me with a zombie or with the exec executing indefinitely. switch(pid = fork()) { case -1:perror("fork failed"); exit(1); case 0: if(key == "cd") { execl("/bin/cd", "cd",... (2 Replies)
Discussion started by: p00ndawg
2 Replies

5. Shell Programming and Scripting

Track Child process exit

hi, I have a job that spawns multiple child processes in background.. Catch is i want to wait for some jobs to finish before i spawn more background processes. (each job creates a file and deletes at the end of it . so i don't want start new jobs after x amount of disk size is used up) now,... (2 Replies)
Discussion started by: ak_saravanan
2 Replies

6. Shell Programming and Scripting

process and exit to new page

File1 --> into shell file for processing --> file2 I have finished the work on my shell processing script, but I need to call this from a form -->cgi-bin, have the form wait/process bar while processing occurs (5-10 seconds) and then have the shell exit gracefully while transferring to the new... (1 Reply)
Discussion started by: dba_frog
1 Replies

7. Shell Programming and Scripting

how to exit status of a piped process ???

Hi, I've searched the related threads both in this forum and others in google and found the solution to be working too in most of the places. But somehow it's not working for me. $cmd | tee -a $LOGFILE & pid=$! wait ${pid} ret=$? echo "$ret" I want the exit status of the $cmd.... (8 Replies)
Discussion started by: ashwini.engr07
8 Replies

8. Shell Programming and Scripting

SSH Process monitoring and Exit Status evaluation

Hi All, I have a peculiar requirement as follows, I have a some hosts on which i have to run a script, so i am using the following code piece for i in $HOSTLIST do ssh ${i} "~/task.sh" done Now i want to run this same thing in parallel on all the hosts and then monitor the ssh process... (1 Reply)
Discussion started by: mihirvora16
1 Replies

9. Shell Programming and Scripting

Catch exit code of specific background process

Hi all, i hava a specific backgroud process. I have de PID of this process. At some time, the process finish his job, is there any way to catch the exit code? I use "echo $?" normally for commands. Thanks! (2 Replies)
Discussion started by: Xedrox
2 Replies

10. Shell Programming and Scripting

Linux process exit

friends when I call to a procedure where DBMS_OUTPUT.PUT_LINE bd are having the procedure? (4 Replies)
Discussion started by: tricampeon81
4 Replies
CLOSE(2)						      BSD System Calls Manual							  CLOSE(2)

NAME
close -- delete a descriptor LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <unistd.h> int close(int d); DESCRIPTION
The close() system call deletes a descriptor from the per-process object reference table. If this is the last reference to the underlying object, the object will be deactivated. For example, on the last close of a file the current seek pointer associated with the file is lost; on the last close of a socket(2) associated naming information and queued data are discarded; on the last close of a file holding an advisory lock the lock is released (see flock(2)). When a process exits, all associated descriptors are freed, but since there is a limit on active descriptors per processes, the close() sys- tem call is useful when a large quantity of file descriptors are being handled. When a process calls fork(2), all descriptors for the new child process reference the same objects as they did in the parent before the fork(). If a new process is then to be run using execve(2), the process would normally inherit these descriptors. Most of the descriptors can be rearranged with dup2(2) or deleted with close() before the execve() is attempted, but if some of these descriptors will still be needed if the execve() fails, it is necessary to arrange for them to be closed only if the execve() succeeds. For this reason, the system call fcntl(d, F_SETFD, 1); is provided, which arranges that a descriptor ``d'' will be closed after a successful execve(); the system call fcntl(d, F_SETFD, 0); restores the default, which is to not close descriptor ``d''. RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
close() will fail if: [EBADF] d is not an active descriptor. [EINTR] An interrupt was received. SEE ALSO
accept(2), execve(2), fcntl(2), flock(2), open(2), pipe(2), socket(2), socketpair(2) STANDARDS
The close() function conforms to ISO/IEC 9945-1:1990 (``POSIX.1''). BSD
April 19, 1994 BSD
All times are GMT -4. The time now is 09:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy