>> Is it possible a user want the log because he/she wants to notice that
>> the system is being attacked?
>
> Yeah, but it doesn't seem very likely, because:
>
> 1. If the system is on the Internet, it's definitely being attacked, and
>
> 2. The attacks that connect to a port and then disconnec
On Wed, Apr 13, 2016 at 10:30 AM, Tatsuo Ishii wrote:
>>> I've also seen it caused by port scanning.
>>
>> Yes, definitely. Question there might be if that's actually a case when we
>> *want* that logging?
>
> Is it possible a user want the log because he/she wants to notice that
> the system is b
>> I've also seen it caused by port scanning.
>>
>
> Yes, definitely. Question there might be if that's actually a case when we
> *want* that logging?
Is it possible a user want the log because he/she wants to notice that
the system is being attacked?
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English:
On Wed, Apr 13, 2016 at 3:56 PM, Tom Lane wrote:
> Magnus Hagander writes:
> > On Wed, Apr 13, 2016 at 10:24 AM, Peter Geoghegan wrote:
> >> On Wed, Apr 13, 2016 at 1:02 AM, Magnus Hagander
> >> wrote:
> >>> It's fairly common to see a lot of "Incomplete startup packet" in the
> >>> logfiles c
Magnus Hagander writes:
> On Wed, Apr 13, 2016 at 10:24 AM, Peter Geoghegan wrote:
>> On Wed, Apr 13, 2016 at 1:02 AM, Magnus Hagander
>> wrote:
>>> It's fairly common to see a lot of "Incomplete startup packet" in the
>>> logfiles caused by monitoring or healthcheck connections.
>> I've also s
On Wed, Apr 13, 2016 at 10:24 AM, Peter Geoghegan wrote:
> On Wed, Apr 13, 2016 at 1:02 AM, Magnus Hagander
> wrote:
> > It's fairly common to see a lot of "Incomplete startup packet" in the
> > logfiles caused by monitoring or healthcheck connections.
>
> I've also seen it caused by port scanni
On Wed, Apr 13, 2016 at 1:02 AM, Magnus Hagander wrote:
> It's fairly common to see a lot of "Incomplete startup packet" in the
> logfiles caused by monitoring or healthcheck connections.
I've also seen it caused by port scanning.
--
Peter Geoghegan
--
Sent via pgsql-hackers mailing list (p
On Wed, Apr 13, 2016 at 9:02 AM, Magnus Hagander wrote:
> It's fairly common to see a lot of "Incomplete startup packet" in the
> logfiles caused by monitoring or healthcheck connections.
>
> I wonder if it would make sense to only log that error if *at least one
> byte* has been received and then
At 2016-04-13 10:02:22 +0200, mag...@hagander.net wrote:
>
> I wonder if it would make sense to only log that error if *at least
> one byte* has been received and then it becomes empty.
Yes, it would be very nice to eliminate that logspam, as you say.
-- Abhijit
--
Sent via pgsql-hackers maili
It's fairly common to see a lot of "Incomplete startup packet" in the
logfiles caused by monitoring or healthcheck connections.
I wonder if it would make sense to only log that error if *at least one
byte* has been received and then it becomes empty. Meaning that if the
client just connects+discon
10 matches
Mail list logo
