openbsd-ports/www/squid/patches/patch-src_cf_data_pre

$OpenBSD: patch-src_cf_data_pre,v 1.32 2011/05/30 20:56:30 sthen Exp $
--- src/cf.data.pre.orig	Mon Nov  9 17:38:57 2009
+++ src/cf.data.pre	Sun May 29 16:36:32 2011
@@ -3738,7 +3738,7 @@ NAME: shutdown_lifetime
 COMMENT: time-units
 TYPE: time_t
 LOC: Config.shutdownLifetime
-DEFAULT: 30 seconds
+DEFAULT: 20 seconds
 DOC_START
 	When SIGTERM or SIGHUP is received, the cache is put into
 	"shutdown pending" mode until all active sockets are closed.
@@ -3787,7 +3787,7 @@ DOC_END
 
 NAME: cache_effective_user
 TYPE: string
-DEFAULT: nobody
+DEFAULT: _squid
 LOC: Config.effectiveUser
 DOC_START
 	If you start Squid as root, it will change its effective/real
@@ -3801,7 +3801,7 @@ DOC_END
 
 NAME: cache_effective_group
 TYPE: string
-DEFAULT: none
+DEFAULT: _squid
 LOC: Config.effectiveGroup
 DOC_START
 	If you want Squid to run with a specific GID regardless of
- reduce the default shutdown_lifetime to 20s; previously it was 30s which is the maximum time rc.subr waits for a daemon, so usually it would end up being forcefully killed (i.e. unclean shutdown -> cache must be rescanned at next startup). suggested by aja@, diff from Brad. - adjust PLIST to prevent warnings with pkg_delete -c, from aja@ ok Brad. 2011-05-30 16:56:30 -04:00			$OpenBSD: patch-src_cf_data_pre,v 1.32 2011/05/30 20:56:30 sthen Exp $
			`--- src/cf.data.pre.orig Mon Nov 9 17:38:57 2009`
			`+++ src/cf.data.pre Sun May 29 16:36:32 2011`
			`@@ -3738,7 +3738,7 @@ NAME: shutdown_lifetime`
			`COMMENT: time-units`
			`TYPE: time_t`
			`LOC: Config.shutdownLifetime`
			`-DEFAULT: 30 seconds`
			`+DEFAULT: 20 seconds`
			`DOC_START`
			`When SIGTERM or SIGHUP is received, the cache is put into`
			`"shutdown pending" mode until all active sockets are closed.`
bug fix update to Squid 2.7-STABLE6, from Brad. 2009-02-08 10:04:33 -05:00			`@@ -3787,7 +3787,7 @@ DOC_END`
use uid/gid of squid:squid instead of nobody:nogroup 2002-02-20 15:31:26 -05:00
			`NAME: cache_effective_user`
			`TYPE: string`
			`-DEFAULT: nobody`
switch to new schema for user/group. -- From: sturm@ Thanks to mpech@ for testing and pointing out the user/group I almost missed in MESSAGE. 2003-07-08 16:43:20 -04:00			`+DEFAULT: _squid`
use uid/gid of squid:squid instead of nobody:nogroup 2002-02-20 15:31:26 -05:00			`LOC: Config.effectiveUser`
upgrade to Squid 2.5.STABLE7 A parsing error exists in the SNMP module of Squid where a specially-crafted UDP packet can potentially cause the server to restart, closing all current connections. 2004-10-20 17:44:20 -04:00			`DOC_START`
			`If you start Squid as root, it will change its effective/real`
bug fix update to Squid 2.7-STABLE6, from Brad. 2009-02-08 10:04:33 -05:00			`@@ -3801,7 +3801,7 @@ DOC_END`
use uid/gid of squid:squid instead of nobody:nogroup 2002-02-20 15:31:26 -05:00
			`NAME: cache_effective_group`
			`TYPE: string`
			`-DEFAULT: none`
switch to new schema for user/group. -- From: sturm@ Thanks to mpech@ for testing and pointing out the user/group I almost missed in MESSAGE. 2003-07-08 16:43:20 -04:00			`+DEFAULT: _squid`
use uid/gid of squid:squid instead of nobody:nogroup 2002-02-20 15:31:26 -05:00			`LOC: Config.effectiveGroup`
			`DOC_START`
upgrade to Squid 2.5.STABLE7 A parsing error exists in the SNMP module of Squid where a specially-crafted UDP packet can potentially cause the server to restart, closing all current connections. 2004-10-20 17:44:20 -04:00			`If you want Squid to run with a specific GID regardless of`