On Tue, Jan 23, 2001 at 02:53:03PM -0600, Bret Hughes <[EMAIL PROTECTED]> wrote:
| I have a sh script named rd that calls another script. The rd script
| loops and reruns the second script infinitely. Occasionally I need to
| bounce rd so I wrote a kill script that sends a signal to the second and
| puts it into a mode that it can be shutdown cleanly and then kills the
| rd script. ( can't kill the second script at this point since rd would
| just restart it) This works great from the command line as the user the
| process runs under. rd shuts down sends a HUP to the subprocess and
| everything is gone. rd is restarted and I am jammin'
rd does not send a HUP. The terminal subsystem sends the HUP.
| The issue is that I get a different behavior when running under cron.
| The second script is suspended ok but when the kill signal is sent to
| rd, the second script does not seem to get a HUP and therefore is not
| shut down.
It's not on a terminal.
| When rd starts back up I have this suspended verison hanging
| around.
|
| Any Ideas? Am I missing something simple here? I figure it might be a
| path thing but don't really know where to start looking. There are no
| errors from cron in the output.
Post your script. We'll rip it to shreds for you.
--
Cameron Simpson, DoD#743 [EMAIL PROTECTED] http://www.zip.com.au/~cs/
"People were happier in my time," says Mr. Faherty, who used to break rocks
for a living. - _Sydney_Morning_Herld_ 25/10/94
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
