Re: Stunnel in inetd mode and PID in logs

On Mon, Dec 05, 2016 at 11:43:06AM +0100, Małgorzata Olszówka wrote:
> The logId option allows you to distinguish log entries generated for 
> each of the connections. Various supported types are useful for the 
> different method of log analysis. But I don’t understand why do you need 
> to have the main stunnel process identifier in the log messages. It can 
> be read from journalctl e.g.

I am not using journalctl. I am running stunnel from tcpserver, and both
are outputting logs to stderr. tcpserver accepts the connections and
reports the PID of each newly spawned connection along with both the
local and remote connection details, but stunnel doesn't report its PID
in its logs.  This makes it impossible to match up the local/remote IP
information with the stunnel logs (TLS negotiation and data transfers).

-- 
Bruce Guenter <[email protected]>                http://untroubled.org/

_______________________________________________
stunnel-users mailing list
[email protected]
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJYSFdbAAoJEFFRvcnBTTxnCGcQALKTD/3gbzZ4QW2Ug8lSIg2S
fYOGI2mmXSAvAYle5EjeEJUl/124XoGJ0MAE8ej192dRyFjs4kp5vf1t7bLK7scs
gJ4RJD9c9Ey4BiGlLLEV9jCxfkRIC2BlXppOQZgdhvtADgYzJI7DSdjkGGiJ1JqK
bUp57Yt3gFeKns0Q1Hk/BTheeH9l6WBJQ3ZLKis/xv+LSeqhLzCydYKdk2yb1hm1
Cl/btiiUezfmMJkbiGSLpAhZyiW5YAKM7nghSpMYhunihp79OLNYt5Yr20DS0oF4
B+XlO3RVwCaimFr+GNvn//8zChewEMHhVwxWanpz1u5DstJM7u6QGyefjCPgGuiw
w7QoiF/qj8OkzOlp+03T1DJA24A8Tbh06k/b4BRH9ynrRhkJaRggkNCBj5FS0gAx
v0RL2/Z75cRO2sU5WoXtNFD1VSA5GMJCNUFZDup3wkz9bEwbwXsIsdGkMoBHM90o
+9IVM3Qrk5gFS+vA8N+XAV6maHcnZPmJLFocFBYFpYge1uBPheO7kO9rgMURg9uD
X2QeiBX7tr476EoS6ilrPipctBr4bH+tWoX87wg6/uuPhaJoSUkjf0EUJ7+Xi+q+
RG/wfn1nc9fSqqHLNzvBzJ3M15HoDofCwv1/iLPvabMTnA9VDR5ahHG6061BJFDi
KVYGLAIA0EcTOSD8gQFQ
=fYVV
-----END PGP SIGNATURE-----