[syslog-ng]program destination prob ?

[Chad Walstrom]

--rwEMma7ioTxnRzrJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 19, 2002 at 12:05:34PM +0200, Thomas Ackermann wrote:
> 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() ?

Run stunnel from inetd on your clients and servers.  Let the inetd
super-server worry about keeping the connection up.  You won't have to
create any special wrapper scripts or worry about PID's.  We used to do
this to provide SSL-ified POP/IMAP access before these daemons started
to incorporate the SSL layer natively.

--=20
Chad Walstrom <chewie@wookimus.net>                 | a.k.a. ^chewie
http://www.wookimus.net/                            | s.k.a. gunnarr

--rwEMma7ioTxnRzrJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8wDpbDMcLGCBsWv0RAi2uAKC/HqorKhlzrnjT2oWacM7eVw0+DgCeLR/l
WVjeSEIrPqIGhzsyO9am3QQ=
=KaU1
-----END PGP SIGNATURE-----

--rwEMma7ioTxnRzrJ--