xinetd dies on occasion, and we'd love to know why (and what to
do about it). any rtfm (with 'm' indicator) or other pointers
gladly accepted.
from /var/log/syslog this morning --
Apr 6 06:36:16 boss xinetd[10615]: {general_handler} (10615) Unexpected signal: 11
(Segmentation f
On Sat, Feb 07, 2004 at 01:15:30PM -0600, daybrown wrote:
> Rob Weir wrote:
>
> >On Thu, Feb 05, 2004 at 03:58:42PM -0800, Barameswari Thoreraj said
> >
> >
> >>hi,
> >>
> >>I am running debian 2.2.19. I had been receiving the message below in my
> >>logs and sendmail has not been able to send or
Rob Weir wrote:
On Thu, Feb 05, 2004 at 03:58:42PM -0800, Barameswari Thoreraj said
hi,
I am running debian 2.2.19. I had been receiving the message below in my
logs and sendmail has not been able to send or receive mail, although it
didn't crash.
This is a very old kernel that has at lea
as at least a couple of security issues.
Upgrade immediately.
> Daemon.log:
> Feb 5 06:19:16 logan xinetd[875]: {general_handler} (875) Unexpected
> signal: 11 (Segmentation fault)
> Feb 5 06:19:16 logan xinetd[875]: {bad_signal} Received 10 signals in 1
> seconds. Exiting...
Ar
hi,
I am running debian 2.2.19. I had been receiving the message below in my
logs and sendmail has not been able to send or receive mail, although it
didn't crash.
Daemon.log:
Feb 5 06:19:16 logan xinetd[875]: {general_handler} (875) Unexpected
signal: 11 (Segmentation fault)
Feb 5 06:
5 matches
Mail list logo