Date: Sun, 18 Feb 2007 12:10:10 +0100 From: "Radim Kolar SF.NET" <hsn@sendmail.cz> To: FreeBSD-gnats-submit@FreeBSD.org Cc: hsn-sf@sd.iol.cz Subject: conf/109272: increase default rc shutdown timeout Message-ID: <E1HIjvm-000G7v-K5@sanatana.dharma> Resent-Message-ID: <200702181120.l1IBK6ap016935@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 109272 >Category: conf >Synopsis: increase default rc shutdown timeout >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Sun Feb 18 11:20:05 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Radim Kolar >Release: FreeBSD 6.2-RELEASE i386 >Organization: >Environment: System: FreeBSD sanatana.dharma 6.2-RELEASE FreeBSD 6.2-RELEASE #1: Sun Jan 14 11:36:17 CET 2007 root@sanatana.dharma:/usr/obj/usr/src/sys/UP i386 >Description: default rcshutdown timeout, 30 seconds is too small. many users runs squid cache and squid cache in default configuration uses 30 second timeout itself before shuting down + time needed to write new store log. Also pgsql database on busy sites needs about 20 seconds to shutdown and fsync datafiles. While busy pgsql are not very common, squid cache is. Default timeout should be increased to meet these demands. Adding 30 more seconds to shutdown timer will no do any harm since programs jammed in shutdown stage are rare and waiting 30 more seconds per jammed shutdown is surviveable. linux distributions are using 60-180 seconds timeout, so FreeBSD 30 second is too small compared to rest of unixes. >How-To-Repeat: run squid in default configuration and on shutdown you will get following error message. rc.shutdown: 30 second watchdog timeout expired. Shutdown terminated. >Fix: change /etc/defaults/rc.conf to rcshutdown_timeout="60" >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1HIjvm-000G7v-K5>