non-interactive shells- nonblocking?
From: Shaddin Doghmi (sfd22_at_cornell.edu)
Date: 07/05/03
- Next message: Stephane CHAZELAS: "Re: string comparison not working"
- Previous message: Dave: "string comparison not working"
- Next in thread: Bill Marcum: "Re: non-interactive shells- nonblocking?"
- Reply: Bill Marcum: "Re: non-interactive shells- nonblocking?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sat, 05 Jul 2003 00:40:42 -0400
According to what ive tried, non-interactive shells that execute a
non-terminating process dont block on that process (dont wait for it to
exit). These shells terminate and exit, and leave the process running. a
bash script that simply executes command Y, where Y is a daemon or
something, immediately exits after starting Y as a process, and doesnt
send a signal to terminate Y. What exactly happens here? is this default
behaviour for non-interactive scripts executing any command Y, or does it
depend on what the command is? Is it because of the lack of a tty? Dont
shells usually wait for the return value of the command? or does it just
skip that when the return value doesnt need to be used for anything ?
could someone elaborate on the rationale and details of this?
- Next message: Stephane CHAZELAS: "Re: string comparison not working"
- Previous message: Dave: "string comparison not working"
- Next in thread: Bill Marcum: "Re: non-interactive shells- nonblocking?"
- Reply: Bill Marcum: "Re: non-interactive shells- nonblocking?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|