SIGABRT from memory is only used when squid deliberately aborts to cause
a core dump, after dumping the reason for the abort in cache.log, such
as an assertion failure.
David.
-- David Luyer Phone: +61 3 9674 7525 Network Development Manager P A C I F I C Fax: +61 3 9699 8693 Pacific Internet (Australia) I N T E R N E T Mobile: +61 4 1111 BYTE http://www.pacific.net.au/ NASDAQ: PCNTF > -----Original Message----- > From: Marc Elsen [mailto:marc.elsen@imec.be] > Sent: Thursday, 14 March 2002 7:47 PM > To: egopfe@hotmail.com > Cc: squid-users@squid-cache.org > Subject: Re: [squid-users] squid dies with signal 6 > > > > > >I'm using squid 2.4stable4 running on a linux slackware 8, > kernel 2.4.18. > >squid is started by the followind command: > >setuidgid squid /usr/squid/bin/squid -d 1 -D > > >the cache starts and work correcly. > >I've noticed that randomnly squid exit with signal 6... No cache.log > >errors... > >Why? What is the potential problem ? > > >here the sysslogd entry: > >.... > > % man 7 signal > > seems to indicate that the application got a SIGABRT. > > Do not directly know why. > Why do you start SQUID in that way ? > > I just use the user and group directives in squid.conf and start > SQUID as root. > > > -- > > 'Time is a consequence of Matter thus > General Relativity is a direct consequence of QM > (M.E. Mar 2002) > >Received on Thu Mar 14 2002 - 02:13:45 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:06:55 MST