Strange Ctrl+C behavior Post: 302997318

Sponsored Content

Top Forums Shell Programming and Scripting Strange Ctrl+C behavior Post 302997318 by bakunin on Thursday 11th of May 2017 09:02:01 AM

05-11-2017

Registered User

The only possible explanation that comes to mind is somehow the nohupped process clinches to the terminal of its parent process. True, nohup should prevent exactly this, but it is the only way what you said could happen. My gut feeling (without being able to prove that, but you might investigate in this direction) is that in fact the rman binary isn't honoring the request to relinquish the terminal correctly. This would also explain why the complaint comes from there.

The following is not really a solution (for this you probably have to contact Oracle and admonish them for their sloppy programming) but may be a workaround: start the script via an at-job, like this:

Code:

echo "my_script.sh > logfile.log 2>&1" | at <sometime>

at, like cron, doesn't provide its parent process a terminal in first place which it could fail to release. Notice, though, that you might have to set more of a working environment than you did now, because your script inherits from your current environment now but would only inherit from init if called from cron/at. init is notoriously poor when it comes to environment.

I hope this helps.

bakunin

bakunin

View Public Profile for bakunin

Find all posts by bakunin

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

strange sed behavior

I have a file called products.kp which contains, for example, 12345678,1^M 87654321,2^M 13579123,3 when I run the command cat products.kp| sed -f kp.sed where kp.sed contains s,^M,, I get the output 12345678,1 87654321,2 13579123,3

2. Shell Programming and Scripting

Very Strange Behavior for redirection

I have searched far and wide for an explanation for some odd behavior for output redirection and haven't come up with anything. A co-worker was working on old scripts which have run for years and embedded in their code were output redirects which worked for the script during execution and then...

3. Shell Programming and Scripting

nawk strange behavior

Dear guys; when deleting repeated lines using nawk as below ; Why the below syntax works? nawk ' !a++' infile > outfile and when using the other below syntax the nawk doesn't work? nawk ' { !a++ } ' infile > outfile or nawk ' { !a++ } ' infile > outfile BR

4. Programming

Strange behavior in C++

I have the following program: int main(int argc, char** argv){ unsigned long int mean=0; for(int i=1;i<10;i++){ mean+=poisson(12); cout<<mean<<endl; } cout<<"Sum of poisson: "<< mean; return 0; } when I run it, I get the...

5. Ubuntu

Ubuntu strange behavior

It is so till login screen. I mean that when I boot my computer, Ubuntu shows a splash screen with mouse instead of Ubuntu logo and in the login screen it shows XUbuntu login screen... It began when I upgraded to previous kernel, I suppose, but I'm not sure... I can't say that it annoys me very...

6. AIX

Strange memory behavior

Hello together, i have a strange memory behavior on a AIX 7.1 System, which i cannot explain. The Filesystem-Cache will not be grow up and drops often after few minutes. I know if a file was deleted, that the same segment in the FS-Cache will also be cleared. But i am not sure if this is the...

7. Shell Programming and Scripting

Strange behavior on one of my server

I am not sure what is wrong, but I have some strange behavior when printing things out. I do create a file with only one word test, no space, no new line etc. nano file<enter> test<ctrl x>y<enter> Server 1 gets (fail) awk '{print "+"$0"*"}' file *test Server 2 gets (OK) awk '{print...

8. AIX

Strange behavior with tar

I am trying to create an archive using tar. I am specifying a list of directories using the -L option. For testing purposes I created a simple directory structure: /backup/test /backup/test/test1 /backup/test/test2 The file specified by the -L option, named files.txt, contains:...

9. Shell Programming and Scripting

Strange behavior of grep

Hi All, I am facing a strange problem while grepping for a process. Here is the small script that i have written. It will look for any process running with the parameter passed to the script. If no process is running it should print appropriate message. $ cat t.ksh #!/bin/ksh set -x ...

LEARN ABOUT NETBSD

nohup

NOHUP(1)						    BSD General Commands Manual 						  NOHUP(1)

NAME

     nohup -- invoke a command immune to hangups

SYNOPSIS

     nohup utility [arg ...]

DESCRIPTION

     The nohup command allows the specified utility to be protected from termination if the user should become logged out (for example, due to a
     modem line or TCP/IP connection being dropped).  To do this, nohup sets the SIGHUP signal(3) (``terminal line hangup'') to be ignored, then
     executes utility along with any arguments.

     If the standard output is a terminal, the standard output is appended to the file nohup.out in the current directory.  If standard error is a
     terminal, it is directed to the same place as the standard output.  If the output file nohup.out cannot be created in the current directory,
     nohup attempts to create the file in the user's home directory.  If the file nohup.out cannot be created, either in the current directory or
     the user's home directory, nohup will exit without invoking utility, with an exit value as described below.

ENVIRONMENT

     The following variable is used by nohup.

     HOME  User's home directory.

EXIT STATUS

     The nohup utility exits with one of the following values:

     126     The utility was found but could not be invoked.

     127     The utility could not be found or an error occurred in nohup.

     Otherwise, the exit status of nohup will be that of utility.

SEE ALSO

     signal(3)

STANDARDS

     The nohup command is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.

BSD
								   July 15, 2005							       BSD