Date: Mon, 5 Apr 2004 14:48:09 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Mipam <mipam@ibb.net> Cc: freebsd-questions@freebsd.org Subject: Re: signal 6 meaning? Message-ID: <20040405134809.GA9043@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <Pine.LNX.4.33.0404051325350.3737-100000@ux1.ibb.net> References: <Pine.LNX.4.33.0404051325350.3737-100000@ux1.ibb.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--SLDf9lqlvOQaIe6s
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Apr 05, 2004 at 01:30:36PM +0200, Mipam wrote:
> Sory for the luser question.
> What's signal 6?
>=20
> kernel: pid 567 (clamd), uid 1006: exited on signal 6
Signal 6 is SIGABRT -- see /usr/include/sys/signal.h. A process dying
with this signal is usually due to it calling the abort(3) function.
That generally indicates that the process itself has found that some
essential pre-requisite for correct function is not available and
voluntarily killing itself, rather than the process being killed by
the kernel because it ran over resource limits or looked at memory
addresses funny or something.
=20
> Where can i rtfm on signals?
> This is in /var/log/clam/clamd.log (so nothing .... :-()
>=20
> +++ Started at Mon Apr 5 13:23:48 2004
> Log file size limited to 2097152 bytes.
> Verbose logging activated.
> Running as user clamav (UID 1006, GID 1007)
> Reading databases from /usr/local/share/clamav
> Protecting against 20832 viruses.
> Unix socket file /var/run/clamav/clamd
> Setting connection queue length to 15
> Listening daemon: PID: 567
> Archive: Archived file size limit set to 10485760 bytes.
> Archive: Recursion level limit set to 5.
> Archive: Files limit set to 1000.
> WARNING: USING HARDCODED LIMIT: Archive: Compression ratio limit set=
to
> 200.
> Archive support enabled.
> RAR support disabled.
> Mail files support enabled.
> OLE2 support disabled.
> Self checking every 3600 seconds.
Hmmm... there should be some sort of explanation logged by the clamav
processes as to why they've elected to abort. You might find running
the daemon in foreground -- possibly under a debugger -- provides more
information. See the 'Foreground' and 'Debug' items in
clamav.conf(5).
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--SLDf9lqlvOQaIe6s
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFAcWOZdtESqEQa7a0RAiMcAJwIkJ11I1CvVFKlcArcY2IndLmLCACfe5pY
k5EsM1DwxvcKuA4r3Yhh+go=
=ycCC
-----END PGP SIGNATURE-----
--SLDf9lqlvOQaIe6s--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040405134809.GA9043>