Oh, sorry, miss understood : Here is my cron information : proxy1:/etc/cron.hourly# more /etc/crontab # /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file. # This file also has a username field, that none of the other crontabs do. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # m h dom mon dow user command 17 * * * * root run-parts --report /etc/cron.hourly 1 0 * * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.daily 47 6 * * 7 root test -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly 52 6 1 * * root test -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly # proxy1:/etc/cron.hourly# ls /etc/cron.hourly/ proxy1:/etc/cron.hourly# As far as I see, there is nothing special on this. One thing I saw witch start every hour is a Digest generation, So I placed : digest_generation off But this didn't changed anything Thanks, L.G. -----Original Message----- From: Henrik Nordstrom [mailto:hno@xxxxxxxxxxxxxxx] Sent: Donnerstag, 3. November 2005 15:07 To: Gix, Lilian (CI/OSR) * Cc: Henrik Nordstrom; squid-users@xxxxxxxxxxxxxxx Subject: RE: Squid unreachable every hour and 6 minutes. On Thu, 3 Nov 2005, Gix, Lilian (CI/OSR) * wrote: > Hello, > > Thanks for your support. > > Unfortunately, my problem happen even if I haven't problem with my > upstream. Didn't ask about your upstream. I asked if you have any crontab entries coinciding with the times your Squid stops responding. > It's right that my extract of the log file is not the best, but as you > can see, the time between those two event is very different. The important message is that there is no message indicating why your Squid terminates before it starts again. Regards Henrik
