On Tue, Jan 28, 2014 at 9:13 AM, Patrick Laimbock <patr...@laimbock.com> wrote:
> On 28-01-14 07:38, Wicher wrote:
>>
>> On Mon, Jan 27, 2014 at 10:35 PM, Patrick Laimbock <patr...@laimbock.com>
>> wrote:
>>
>>> 6403 socket(PF_FILE, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 25
>>> 6403 connect(25, {sa_family=AF_FILE, path="/dev/log"}, 110) = 0
>>> 6403 sendto(25, "<20>Jan 27 22:11:59 dspam[6372]:"..., 119,
>>> MSG_NOSIGNAL, NULL, 0) = 119
>>> 6403 close(25) = 0
>>
>>
>> I'm curious — what did it write to the system log just before segfaulting?
>
>
> Hi Wicher,
>
> I couldn't find anything:
>
Well that's exceedingly odd as dspam even manages to close the file
descriptor after sending the message to your system logger...
(/dev/log is the socket that your logger is listening on.).
Dspam didn't crash *during* the sending, so then where did the message
go? Could you check your syslog configuration?
Regards, Wicher
------------------------------------------------------------------------------
WatchGuard Dimension instantly turns raw network data into actionable
security intelligence. It gives you real-time visual feedback on key
security issues and trends. Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
_______________________________________________
Dspam-user mailing list
Dspam-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspam-user
