Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
33
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line
33
Strict Standards: Only variables should be assigned by reference in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/post.php on line
173
«
firefox ala widefox
Strict Standards: Only variables should be assigned by reference in
/homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/post.php on line
173
Wein des Monats »
Im vorliegenden Fall installieren wir squid3 unter Debian Etch.
# apt-get install squid3
Damit squid Anfragen weiterleitet müssen zunächst die ACL’s innerhalb der squid.conf angepasst werden. Wir machen es uns einfach und erlauben die ACL all
(die den Zugriff auf 0/0 gewährt) generell:
http_access allow all
Damit sich das Chaching auch lohnt setzen wir den Zwischenspeicher hoch
cache_dir ufs /var/spool/squid3 1000 16 256
das wären 1000MB bei 16 1st-Level und 256 2nd-Level Directories
und weisen squid an Daten bis zu 100 MB zu cachen:
maximum_object_size 100 MB
In einem Windows Netzwerk ohne “Software Update Service” kann ein Proxy richtig viel Bandbreite sparen! Gerade an Patch-Days wo Microsoft viele Updates frei gibt, kann es in einer Firma mit vielen PCs, aber ohne SUS, ziemlich eng auf der Leitung werden.
WICHTIG: Damit windowsupdate die Proxy-Einstellungen des Internet-Explorers verwendet muss man ihm dies noch mitteilen:
proxycfg -u
This entry was posted on
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 33
Sunday, October 28th, 2007 at
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 19
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 28
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 30
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 32
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/21/d19413512/htdocs/SITES/haegele.info/tim/wp-includes/functions.php on line 33
18:54 and is filed under IT.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
Leave a Reply
You must be logged in to post a comment.