Chad Walstrom on Fri, Apr 19, 2002 at 10:40:11AM -0500: Hi,
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.
you could also run stunnel standalone (from /etc/rc or init-scripts), doing something like: client: stunnel -c -d localhost:514 -r loghost:8514 server: stunnel -d 8514 -r localhost:514 Then make syslog-ng on the server listen on localhost:514 only and make syslog-ng on the clients log to localhost:514. I don't want things that should be running all the time started from inetd. If you really want to keep it minimal, you could check if there is a option in stunnel not to start it in the background, and then run it from inittab with "respawn" :) Regards, -- ____ ____ / _/| - > Gregor Binder <gb@(rootnexus.net|sysfive.com)> | / || _\ \ \__ Id: 0xE2F31C4B Fp: 8B8A 5CE3 B79B FBF1 5518 8871 0EFB AFA3 E2F3 1C4B