Problem when forking
Rodrigo Barboza <[email protected]> Tue, 17 Mar 2015 11:21:02 -0300
| Newsgroups | gmane.comp.db.postgresql.interfaces |
|---|---|
| Message-ID | <CANs8QJYUu4QYpGV963_xdBjX+gUWAMFct_-At80KtvzwHdqzqg@mail.gmail.com> |
--20cf301d414e92fd2405117cae0b Content-Type: text/plain; charset=UTF-8 Hello everyone, I am seeing too many messages like "unexpected EOF on client connection". I've made a reasearch and I know the reason: I have processes that fork and don't close the connection causing those warnings. My questions is: is there a way to avoid that behavior beside of closing the connection before forking? Maybe close the file descriptor without closing the connection... This is not causing any trouble, but my log increases very quickly with useless information. --20cf301d414e92fd2405117cae0b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hello everyone,<div><br></div><div>I am seeing too many me= ssages like "unexpected EOF on client connection".</div><div>I= 9;ve made a reasearch and I know the reason: I have processes that fork and= don't close the connection causing those warnings.</div><div><br></div= ><div>My questions is: is there a way to avoid that behavior beside of clos= ing the connection before forking?=C2=A0</div><div><br></div><div>Maybe clo= se the file descriptor without closing the connection...</div><div><br></di= v><div>This is not causing any trouble, but my log increases very quickly w= ith useless information.</div></div> --20cf301d414e92fd2405117cae0b--