Hello, all

I've got the following "problem" today when I checked my FreeBSD 4.6 /var/log/messages file:

Nov 1 03:01:01 pantcho /kernel: pid 32984 (su), uid 0: exited on signal 10 (core dumped)
Nov 2 03:01:00 pantcho /kernel: pid 34341 (su), uid 0: exited on signal 10 (core dumped)
Nov 2 04:15:01 pantcho /kernel: pid 34622 (su), uid 0: exited on signal 10 (core dumped)
Nov 3 03:01:00 pantcho /kernel: pid 37952 (su), uid 0: exited on signal 10 (core dumped)
Nov 4 03:01:00 pantcho /kernel: pid 39283 (su), uid 0: exited on signal 10 (core dumped)
Nov 4 10:53:45 pantcho su: BAD SU utopia to root on /dev/ttyp0
Nov 4 10:53:52 pantcho su: BAD SU utopia to root on /dev/ttyp0
Nov 4 10:53:57 pantcho su: utopia to root on /dev/ttyp0

The system where I got this message is up and running for two months since now but this is the first occurence of this message. I'm curious what is the reason for the SU's core dumping and also what is the reason for making SU active. The "ugly" thing is only these are the messages in /var/log/mesages in the period from 1 of October until 4 at the morning. These 4 days the system was up but nobody uses it because of a holiday days.
Also I make two wrong and one right atempts to SU to root in order to check the syntax of the logged messages and it seems that the "core dumped" messages are not issued by an user trying to get root. Also it looks like the kernel itself issues SU because instead of program name the owner of the SU process is /kernel.
So that's my so called problem :) I'll appreciate any clue on what is the reasons for this behaviour.

Regards

Reply via email to