17f86c3675
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.
31 lines
870 B
Plaintext
31 lines
870 B
Plaintext
$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
|