Sponsored Content
Full Discussion: Strange Ctrl+C behavior
Top Forums Shell Programming and Scripting Strange Ctrl+C behavior Post 302997318 by bakunin on Thursday 11th of May 2017 09:02:01 AM
Old 05-11-2017
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
 

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 (5 Replies)
Discussion started by: Kevin Pryke
5 Replies

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... (5 Replies)
Discussion started by: cahook
5 Replies

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 Replies)
Discussion started by: ahmad.diab
4 Replies

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... (4 Replies)
Discussion started by: santiagorf
4 Replies

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 Replies)
Discussion started by: Sapfeer
6 Replies

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... (8 Replies)
Discussion started by: -=XrAy=-
8 Replies

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... (9 Replies)
Discussion started by: Jotne
9 Replies

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:... (8 Replies)
Discussion started by: judykstra
8 Replies

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 ... (9 Replies)
Discussion started by: veeresh_15
9 Replies
nohup(1)						      General Commands Manual							  nohup(1)

NAME
nohup - run a command immune to hangups SYNOPSIS
command [arguments] DESCRIPTION
executes command with hangups and quits ignored. If output is not redirected by the user, both standard output and standard error are sent to If is not writable in the current directory, output is redirected to otherwise, fails. If a file is created, the file's permission bits will be set to If output from is redirected to a terminal, or is not redirected at all, the output is sent to EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified in the environment or is set to the empty string, the value of is used as a default for each unspecified or empty vari- able. If is not specified or is set to the empty string, a default of "C" (see lang(5)) is used instead of If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to "C". See environ(5). International Code Set Support Single- and multi-byte character code sets are supported. EXAMPLES
It is frequently desirable to apply to pipelines or lists of commands. This can be done only by placing pipelines and command lists in a single file, called a shell script. To run the script using features apply to the entire contents of file. If the shell script file is to be executed often, the need to type can be eliminated by setting execute permission on file. The script can also be run in the background with interrupts ignored (see sh(1)): file typically contains normal keyboard command sequences that one would want to continue running in case the terminal disconnects, such as: WARNINGS
Be careful to place punctuation properly. For example, in the command form: applies only to command1. To correct the problem, use the command form: Be careful of where standard error is redirected. The following command may put error messages on tape, making it unreadable: whereas puts the error messages into file EXIT STATUS
The following exit values are returned: The command specified by command was found but could not be invoked An error occurred in the nohup utility or the specified command could not be found Otherwise, the exit status of nohup will be that of the command specified. SEE ALSO
chmod(1), nice(1), sh(1), signal(5). STANDARDS CONFORMANCE
nohup(1)
All times are GMT -4. The time now is 06:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy