From: Koichi S. <koi...@gm...> - 2013-01-10 10:08:31
|
Michael; Thanks for a good comment. I don't think discussing why is productive. Because gtm_ctl is expected to behave similarly to pg_ctl, if pg_ctl -l works nicely to redirect stdout/stderr with -l option, I think we should improve gtm_ctl as well. Regards; ---------- Koichi Suzuki 2013/1/10 Michael Meskes <me...@po...>: > On Wed, Jan 09, 2013 at 05:40:35PM +0900, Koichi Suzuki wrote: >> Yes, we have a similar problem using gtm_ctl with ssh. And this >> happens in pg_ctl as well. >> >> ssh hostxx pg_ctl start -Z coordinator -D somedirs >> >> won't return either. As you suggested, we have to redirect >> stdout/stderr explicitly. >> >> I think I can fix this problem for gtm_ctl by taking care of >> stdout/stderr. But I don't think I should do the same thing to >> pg_ctl. > > I think this is a feature and not a bug. The bug just comes up when using the > "-l" option to redirect output to a log file. Without this option you can argue > the user wants stdout/stderr to remain open to see the messages coming from the > backend. With a log file redirection stdout/stderr should be gone. This works > nicely with pg_ctl as both, stdout and stderr, get redirected to the logfile. > With gtm_ctl, however, only stderr gets redirected. Now the question is why... > > Michael > -- > Michael Meskes > Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) > Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org > Jabber: michael.meskes at gmail dot com > VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL |