On Fri, Apr 19, 2002 at 12:05:34PM +0200, Thomas Ackermann wrote:
hy! i'm using syslog-ng to send remote log messages over an stunnel to a log server. everything's running quite fine, besides one little problem i have..
i'm starting the stunnel with program("/usr/sbin/stunnel -r 192.168.3.125:6543 -c");
when the stunnel is killed or quits because of a bad connection, syslog-ng doesn't even bother 'bout trying to restart it. is that a wanted behaviour and, or, is there a way to gat syslog-ng to respawn processes called with program() ?
no, currently this is the intended behaviour. try running a wrapper script around stunnel, which restarts it if necessary. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1