Re: Stunnel in inetd mode and PID in logs

Małgorzata Olszówka <[email protected]>
Newsgroups gmane.network.stunnel.user
Message-ID <[email protected]>
W dniu 08.12.2016 o 15:25, Bruce Guenter pisze:
> On Thu, Dec 08, 2016 at 09:52:41AM +0100, Małgorzata Olszówka wrote:
>> Could you try to update stunnel to the latest 5.39 beta version and set
>> logId=process id the global options.
>> Now, stunnel is able to report its PID in its logs. Is this ok?
>
> No, it still reports (for example):
>
> 2016.12.08 08:22:08 LOG5[ui]: Service [smtps] accepted connection
>

Yes, but when the service is started, you can see PID in the next logs:

2016.12.08 11:38:59 LOG7[ui]: Service [https] accepted (FD=3) from 
127.0.0.1:59400
2016.12.08 11:38:59 LOG7[16226]: Service [https] started
2016.12.08 11:38:59 LOG7[16226]: Option TCP_NODELAY set on local socket
2016.12.08 11:38:59 LOG5[16226]: Service [https] accepted connection 
from 127.0.0.1:59400
2016.12.08 11:38:59 LOG6[16226]: s_connect: connecting 127.0.0.1:443
...

# ps aux | grep stunnel
root     16226  0.0  0.5 239860  5828 pts/0    Sl+  11:38   0:00 stunnel

---
Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast.
https://www.avast.com/antivirus

_______________________________________________
stunnel-users mailing list
[email protected]
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.