No subject

hours.

The panic's soon followed:

Jul 25 07:40:26 10.17.0.1 smbd[14293]: [2002/07/25 07:40:26, 0]
lib/fault.c:fault_report(38) =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]: [2002/07/25 07:40:26, 0]
lib/fault.c:fault_report(39) =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]:   INTERNAL ERROR: Signal 11 in
pid 14293 (2.2.4) =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]:   Please read the file BUGS.txt
in the distribution =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]: [2002/07/25 07:40:26, 0]
lib/fault.c:fault_report(41) =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]: [2002/07/25 07:40:26, 0]
lib/util.c:smb_panic(1092) =20
Jul 25 07:40:26 10.17.0.1 smbd[14293]:   PANIC: internal error =20


Note that this isn't the same PID...

I can't seem to couple a crashing instance with the other log message.
Perhaps it's a parent process SEGVing and these are child processes,
or vice versa. (although I see a lot more than 2 processes spewing
the PDC related messages, and a lot more than 2 panic'ing, odd.)

Thanks,
Nir.

--
Nir Soffer -=3D- Software Engineer, Exanet Inc. -=3D-
"Father, why are all the children weeping? / They are merely crying son
 O, are they merely crying, father? / Yes, true weeping is yet to come"
        -- Nick Cave and the Bad Seeds, The Weeping Song>=20