On Tue, Apr 27, 2010 at 11:17 AM, Ron <rg.li...@rzweb.com> wrote: > After I did a big portupgrade on the April 25th, I am now getting a lot > these... > > +pid 53508 (conftest), uid 0: exited on signal 11 (core dumped) > +pid 28553 (smtp), uid 125: exited on signal 11 > +pid 28569 (smtp), uid 125: exited on signal 11 > +pid 28657 (smtp), uid 125: exited on signal 11 > > ..in my logs. I've tried forcing a rebuild of postfix and all dependency to > no avail. I don't seem to be loosing any email. > > I'm assuming it's postfix (I don't use sendmail), but I could be wrong. > Anyone know what this is or where I should start looking? Did I not upgrade > something correctly after the big changes? > > Thanks
Signal 11, or SIGSEGV, is a segmentation violation. It occurs when a program makes an invalid memory reference. The program exits (crashes) and leaves a dump of it's memory image on the file system somewhere. The memory image, a .core file, is somewhere on your file system and will allow the application (I assume Postfix) to be debugged (using gdb). -Brandon _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"