Closing stdout upon startup
2013-07-27 by Jim Klimov
Hello all, I am facing an issue on a host where I tried new milter-greylist (4.3.3 with patches for chown) - my old init-script used on many installations with much older greylists includes parsing of output via grep so as to report a little on the console during startup. This currently hangs the initscript, with grep apparently waiting for input. I also tried to to OUT=`milter-greylist $OPTIONS` in order to parse the $OUT variable contents - but to the same effect, this subshell never exits. I also tried '-D' option paired with '&' to background the milter started in no-fork mode. If I ctrl+break the script, milter is running in the background (if started without -D), however. So far the only working workaround was to not parse this output completely, which is valid but uncool - and a regression compared to older versions ;) By guess, this may have to do with (not) closing stdout in some way after the initialization and reporting on it has completed (i.e. which ACLs were loaded, etc.) Does this ring a bell? Were there any similar changes, perhaps in the past 2-3 years? (The other hosts are quite aged, yes). Thanks, //Jim Klimov