Non-interactive shell leaves children running when signaled by TERM
Hello.
When I run
and then send SIGTERM to sh's pid, both sh and yes dies.
When I run
and then send SIGTERM to sh's pid, sh dies but yes and sed remain running in background with init as the parent.
Why?
I bash man page is stated that when bash is interactive and it receives SIGHUP, it sends SIGHUP to all its child processes.
Is it possible to achieve something similar when shell is non-interactive (ie. kill all child processes upon delivery of signal before exit)?
Thank you.
---------- Post updated at 10:05 PM ---------- Previous update was at 08:35 PM ----------
So I've got answer for the first question. It's because in first case shell just call exec, so the signal is delivered to yes. But in the second case, sh do 2 x fork and 2 x exec and waits for the child processes.
NEWS:
Flaw leaves Linux computers vulnerable
http://news.com.com/2100-1001-857265.html
A flaw in a software-compression library used in all versions of Linux could leave the lion's share of systems based on the open-source operating system open to attack, said sources in the security... (3 Replies)
hi floks !
i'd like to know how can i transmete a character or a string from my source code to a term and make it interpret or un by the shell wich is running in my term.
I'd like to create a Term from my code (and get its file descriptor) and then transmete each char typed on the keyboard to... (1 Reply)
now, i have a program that i would very much prefer to run remotely as i hate having to log into the box it is on.
the problem is, every command i have tried to run this remotely doesn't work.
the commands tries to kick off the program on the remote box but then hangs.
like take for... (3 Replies)
Hi All,
I have an input_file below and i would like to use Perl to search for the term "aaa" and output the 3rd term in the same row as "aaa".For Example, i want to search for the term "ddd" and would want the code to ouput the 3rd term in the same row which is "fff". Can somebody help ?
... (28 Replies)
Q. Write a script that behaves both in interactive and non interactive mode. When no arguments are supplied it picks up each C program from the directory and prints first 10 lines.
It then prompts for deletion of the file.
If user supplies arguments with the script , then it works on those files... (1 Reply)
Q. Write a script that behaves both in interactive and non interactive mode. When no arguments are supplied it picks up each C program from the directory and prints first 10 lines.
It then prompts for deletion of the file.
If user supplies arguments with the script , then it works on those files... (8 Replies)
I'm new to working with pipes, so I don't know whether the following is expected behaviour or a bug on the part of an application.
Since Version 0.47, Inkscape provides a non-GUI interactive shell mode of operation. I am trying to time the program's performance in converting SVG files to PNG... (1 Reply)
Is there a way to find out the path/name of a script file that signaled my process? All that shows up from the signal info data is ksh. Even in getprocs64 is is just ksh. I am not sure why the full path and file name are not showing up instead of the shell name. I tried ptrace64 with PT_LDINFO but... (4 Replies)
Hi,
I have a script that calles some other scripts. Those scripts are expecting some inputs.
Right no I am typing manually. But now the number of questions from other scripts are too much and I want to give asnwers autimatically.
example.
Other scripts gives me 2 options
1) joom... (2 Replies)
Hi Guys,
Excuse if am asking silly Que ... :rolleyes:
Please explain me whats difference between login and interactive shell in Linux .. Have googled but still in doubt .. :confused:
--Shirish Shukla (4 Replies)
Discussion started by: Shirishlnx
4 Replies
LEARN ABOUT DEBIAN
proc::syncexec
SyncExec(3pm) User Contributed Perl Documentation SyncExec(3pm)NAME
Proc::SyncExec - Spawn processes but report exec() errors
SYNOPSIS
# Normal-looking piped opens which properly report exec() errors in $!:
sync_open WRITER_FH, "|command -with args" or die $!;
sync_open READER_FH, "command -with args|" or die $!;
# Synchronized fork/exec which reports exec errors in $!:
$pid = sync_exec $command, @arg;
$pid = sync_exec $code_ref, $cmd, @arg; # run code after fork in kid
# fork() which retries if it fails, then croaks() if it still fails.
$pid = fork_retry;
$pid = fork_retry 100; # retry 100 times rather than 5
$pid = fork_retry 100, 2; # sleep 2 rather than 5 seconds between
# A couple of interfaces similar to sync_open() but which let you
# avoid the shell:
$pid = sync_fhpopen_noshell READERFH, 'r', @command;
$pid = sync_fhpopen_noshell WRITERFH, 'w', @command;
$fh = sync_popen_noshell 'r', @command_which_outputs;
$fh = sync_popen_noshell 'w', @command_which_inputs;
($fh, $pid) = sync_popen_noshell 'r', @command_which_outputs;
($fh, $pid)= sync_popen_noshell 'w', @command_which_inputs;
DESCRIPTION
This module contains functions for synchronized process spawning with full error return. If the child's exec() call fails the reason for
the failure is reported back to the parent.
These functions will croak() if they encounter an unexpected system error, such as a pipe() failure or a repeated fork() failure.
Nothing is exported by default.
fork_retry [max-retries [sleep-between]]
This function runs fork() until it succeeds or until max-retries (default 5) attempts have been made, sleeping sleep-between seconds
(default 5) between attempts. If the last fork() fails fork_retry croak()s.
sync_exec [code] command...
This function is similar to a fork()/exec() sequence but with a few twists.
sync_exec does not return until after the fork()ed child has already performed its exec(). The synchronization this provides is useful
in some unusual circumstances.
Normally the pid of the child process is returned. However, if the child fails its exec() sync_exec returns undef and sets $! to the
reason for the child's exec() failure.
Since the @cmd array is passed directly to Perl's exec() Perl might choose to invoke the command via the shell if @cmd contains only
one element and it looks like it needs a shell to interpret it. If this happens the return value of sync_exec only indicates whether
the exec() of the shell worked.
The optional initial code argument must be a code reference. If it is present it is run in the child just before exec() is called.
You can use this to set up redirections or whatever. If code returns false no exec is performed, instead a failure is returned using
the current $! value (or EINTR if $! is 0).
If the fork() fails or if there is some other unexpected system error sync_exec croak()s rather than returning.
sync_fhpopen_noshell fh type cmd [arg]...
This is a popen() but it never invokes the shell and it uses sync_exec() under the covers. See "sync_exec".
The type is either 'r' to read from the process or 'w' to write to it.
The return value is the pid of the forked process.
sync_popen_noshell type cmd arg...
This is like sync_fhpopen_noshell, but you don't have to supply the filehandle.
If called in an array context the return value is a list consisting of the filehandle and the PID of the child. In a scalar context
only the filehandle is returned.
sync_open fh [open-spec]
This is like a Perl open() except that if a pipe is involved and the implied exec() fails sync_open() fails with $! set appropriately.
See "sync_exec".
Like sync_exec, sync_open croak()s if there is an unexpected system error (such as a failed pipe()).
Also like sync_exec, if you use a command which Perl needs to use the shell to interpret you'll only know if the exec of the shell
worked. Use sync_fhpopen_noshell or sync_exec to be sure that this doesn't happen.
AUTHOR
Roderick Schertler <roderick@argon.org>
SEE ALSO perl(1).
perl v5.8.8 2005-02-04 SyncExec(3pm)