AW: enable-async-io breaks -USR1 logrotate?

Hi!

I once had a simmilar problem. Worst was, that even the RunCache script was
thinking that squid was not running and tried to restart it over and over
again.

PS: ACHTUNG!! Neue Einheitsnummer 0840 840 850 !!
!! Gültig für die ganze Schweiz !!

Mit freundlichen Grüssen

Patrick Kormann
DataComm (Schweiz) AG
Projektleiter Technik

-- 
PGP Fingerprint: B52F 7B90 0DDE AADE A388  1E9B 43A6 5555 FC47 04EB 
-----Ursprüngliche Nachricht-----
Von: Matija Grabnar [mailto:Matija.Grabnar@arnes.si]
Gesendet am: Donnerstag, 15. April 1999 10:41
An: pkormann@intern.datacomm.ch
Cc: squid-users@ircache.net; Matija.Grabnar@arnes.si
Betreff: Re: enable-async-io breaks -USR1 logrotate?
> 
> A few days ago I recompiled Squid 2.1.PATCH2 with --enable-async-io on
> Linux 2.2.4 RH5.1 glibc 2.0.7.  Since then, it appears that squid no
> longer responds to -USR1 to rotate logs.  I noticed after the HD filled.
I use async io on Solaris 2.5.1 and I have notic3ed a simmilar problem.
Note that logrotate does not fail immediately: it works for a week or more,
and then it starts responding to "-k rotate" with "no running copy" even
though
squid is running and responding to requests. 
-- 
"My name is Not Important. Not to friends. 
    But you can call me mr. Important"  - Not J. Important 
Matija.Grabnar@arnes.si