Re: pipes, scripts, and launchd
Re: pipes, scripts, and launchd
- Subject: Re: pipes, scripts, and launchd
- From: Perry Smith <email@hidden>
- Date: Fri, 28 Dec 2007 20:20:05 -0600
On Dec 28, 2007, at 3:21 PM, Michael Smith wrote:
On Dec 28, 2007, at 12:03 PM, email@hidden
wrote:
I may be making too big a deal of all this but I can't figure out how
to do something like:
postgres <args> | rotatelogs <args>
from launchd. If I put that command in a simple bash shell script, I
*believe* it will not work. The signal will go to bash and bash will
not pass it along to the children.
There's something missing from what you're asking here;
specifically, what signal are you talking about?
launchd uses SIGTERM to signal the process should gracefully
shutdown. Then launchd does a SIGKILL when it gets impatient.
I could trap the signal and pass it along myself... but, $! gives the
pid for the last process in the pipe (rotatelogs). That is not
what I
need to signal. I need the signal passed to postgres. And, in fact,
it would be nice if the signal did NOT pass to rotatelogs. I'd like
for it to stop when its input closes and not before then.
Are you actually trying to pass output from postgres to rotatelogs,
or just have the two die cleanly together?
Yes, I am trying to pass output from postgres to rotatelogs.
rotatelogs is a cute way to have your log files age.
If the latter, then that's not a good way to do it.
Anyone have any suggestions of how to do this?
What is "this"?
Have the output from the daemon go to the input of another process.
Thanks,
pedz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden