4 >The Main Configuration File</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.4 User Manual"
11 HREF="index.html"><LINK
13 TITLE="Privoxy Configuration"
14 HREF="configuration.html"><LINK
17 HREF="actions-file.html"><LINK
20 HREF="../p_doc.css"></HEAD
31 SUMMARY="Header navigation table"
40 >Privoxy 3.0.4 User Manual</TH
48 HREF="configuration.html"
62 HREF="actions-file.html"
78 >7. The Main Configuration File</H1
80 > Again, the main configuration file is named <TT
84 Linux/Unix/BSD and OS/2, and <TT
88 Configuration lines consist of an initial keyword followed by a list of
89 values, all separated by whitespace (any number of spaces or tabs). For
100 >confdir /etc/privoxy</I
107 > Assigns the value <TT
114 > and thus indicates that the configuration
115 directory is named <SPAN
117 >"/etc/privoxy/"</SPAN
120 > All options in the config file except for <TT
127 > are optional. Watch out in the below description
128 for what happens if you leave them unset.</P
130 > The main config file controls all aspects of <SPAN
134 operation that are not location dependent (i.e. they apply universally, no matter
135 where you may be surfing).</P
143 >7.1. Configuration and Log File Locations</H2
148 > can (and normally does) use a number of
149 other files for additional configuration, help and logging.
150 This section of the configuration file tells <SPAN
154 where to find those other files. </P
156 > The user running <SPAN
160 permission for all configuration files, and write permission to any files
161 that would be modified, such as log files and actions files.</P
179 >The directory where the other configuration files are located</P
191 >/etc/privoxy (Unix) <SPAN
200 > installation dir (Windows) </P
203 >Effect if unset:</DT
227 > When development goes modular and multi-user, the blocker, filter, and
228 per-user config will be stored in subdirectories of <SPAN
232 For now, the configuration directory structure is flat, except for
235 >confdir/templates</TT
236 >, where the HTML templates for CGI
237 output reside (e.g. <SPAN
263 > The directory where all logging takes place (i.e. where <TT
283 >/var/log/privoxy (Unix) <SPAN
292 > installation dir (Windows) </P
295 >Effect if unset:</DT
329 >7.1.3. actionsfile</H4
331 NAME="DEFAULT.ACTION"
334 NAME="STANDARD.ACTION"
349 HREF="actions-file.html"
358 >File name, relative to <TT
377 CLASS="LITERALLAYOUT"
378 > standard # Internal purposes, no editing recommended</P
385 CLASS="LITERALLAYOUT"
386 > default # Main actions file</P
393 CLASS="LITERALLAYOUT"
394 > user # User customizations</P
404 >Effect if unset:</DT
407 > No actions are taken at all. Simple neutral proxying.
417 > lines are permitted, and are in fact recommended!
421 The default values include standard.action, which is used for internal
422 purposes and should be loaded, default.action, which is the
426 > actions file maintained by the developers, and
430 >, where you can make your personal additions.
434 Actions files are where all the per site and per URL configuration is done for
435 ad blocking, cookie management, privacy considerations, etc.
436 There is no point in using <SPAN
440 least one actions file.
453 >7.1.4. filterfile</H4
455 NAME="DEFAULT.FILTER"
467 HREF="filter-file.html"
476 >File name, relative to <TT
485 >default.filter (Unix) <SPAN
491 > default.filter.txt (Windows)</P
494 >Effect if unset:</DT
497 > No textual content filtering takes place, i.e. all
501 HREF="actions-file.html#FILTER"
510 actions in the actions files are turned neutral.
520 > lines are permitted.
524 HREF="filter-file.html"
526 > contain content modification
528 HREF="appendix.html#REGEX"
529 >regular expressions</A
530 >. These rules permit
531 powerful changes on the content of Web pages, and optionally the headers
532 as well, e.g., you could disable your favorite JavaScript annoyances,
533 re-write the actual displayed text, or just have some fun replacing
540 > wherever it appears
548 HREF="actions-file.html#FILTER"
557 actions rely on the relevant filter (<TT
563 to be defined in a filter file!
566 > A pre-defined filter file called <TT
570 a number of useful filters for common problems is included in the distribution.
571 See the section on the <TT
574 HREF="actions-file.html#FILTER"
581 > It is recommended to place any locally adapted filters into a separate
608 > The log file to use
615 >File name, relative to <TT
624 >logfile (Unix) <SPAN
630 > privoxy.log (Windows)</P
633 >Effect if unset:</DT
636 > No log file is used, all log messages go to the console (<TT
646 > The logfile is where all logging and error messages are written. The level
647 of detail and number of messages are set with the <TT
651 option (see below). The logfile can be useful for tracking down a problem with
655 > (e.g., it's not blocking an ad you
656 think it should block) but in most cases you probably will never look at it.
659 > Your logfile will grow indefinitely, and you will probably want to
660 periodically remove it. On Unix systems, you can do this with a cron job
664 >). For Red Hat, a <B
668 script has been included.
671 > On SuSE Linux systems, you can place a line like <SPAN
674 +1024k 644 nobody.nogroup"</SPAN
679 the effect that cron.daily will automatically archive, gzip, and empty the
680 log, when it exceeds 1M size.
683 > Any log files must be writable by whatever user <SPAN
687 is being run as (default on UNIX, user id is <SPAN
713 > The file to store intercepted cookies in
720 >File name, relative to <TT
729 >jarfile (Unix) <SPAN
735 > privoxy.jar (Windows)</P
738 >Effect if unset:</DT
741 > Intercepted cookies are not stored at all.
748 > The jarfile may grow to ridiculous sizes over time.
761 >7.1.7. trustfile</H4
771 > The trust file to use
778 >File name, relative to <TT
791 >Unset (commented out)</I
793 >. When activated: trust (Unix) <SPAN
799 > trust.txt (Windows)</P
802 >Effect if unset:</DT
805 > The entire trust mechanism is turned off.
812 > The trust mechanism is an experimental feature for building white-lists and should
813 be used with care. It is <SPAN
819 > recommended for the casual user.
822 > If you specify a trust file, <SPAN
826 access to sites that are specified in the trustfile. Sites can be listed
833 > character limits access to this site
834 only (and any sub-paths within this site), e.g.
837 >~www.example.com</TT
841 > Or, you can designate sites as <SPAN
845 >trusted referrers</I
848 prepending the name with a <TT
851 > character. The effect is that
852 access to untrusted sites will be granted -- but only if a link from this
853 trusted referrer was used. The link target will then be added to the
857 > so that future, direct accesses will be granted.
858 Sites added via this mechanism do not become trusted referrers themselves
859 (i.e. they are added with a <TT
868 > operator in the trust file, it may grow
869 considerably over time.
872 > It is recommended that <SPAN
881 >--disable-toggle</TT
885 > --disable-editor</TT
886 > options, if this feature is to be
890 > Possible applications include limiting Internet access for children.
904 >7.2. Local Set-up Documentation</H2
906 > If you intend to operate <SPAN
910 than just yourself, it might be a good idea to let them know how to reach
911 you, what you block and why you do that, your policies, etc.
920 >7.2.1. user-manual</H4
930 > Location of the <SPAN
940 >A fully qualified URI</P
955 >Effect if unset:</DT
959 HREF="http://www.privoxy.org/user-manual/"
961 >http://www.privoxy.org/<TT
968 will be used, where <TT
983 > The User Manual URI is used for help links from some of the internal CGI pages.
984 The manual itself is normally packaged with the binary distributions, so you probably want
985 to set this to a locally installed copy. For multi-user setups, you could provide a copy on
986 a local webserver for all your users and use the corresponding URL here.
992 > Unix, in local filesystem:
1003 >  user-manual  file:///usr/share/doc/privoxy-3.0.4/user-manual/</PRE
1010 > Windows, in local filesystem, <SPAN
1016 > use forward slash notation:
1027 >  user-manual  file:/c:/some-dir/privoxy-3.0.4/user-manual/</PRE
1034 > Windows, UNC notation (with forward slashes):
1045 >  user-manual  file://///some-server/some-path/privoxy-3.0.4/user-manual/</PRE
1052 > Any platform, on local webserver (called <SPAN
1054 >"local-webserver"</SPAN
1066 >  user-manual  http://local-webserver/privoxy-user-manual/</PRE
1091 > If set, this option should be <SPAN
1095 >the first option in the config
1098 >, because it is used while the config file is being read.
1113 NAME="TRUST-INFO-URL"
1115 >7.2.2. trust-info-url</H4
1119 CLASS="VARIABLELIST"
1125 > A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
1138 >Two example URL are provided</P
1141 >Effect if unset:</DT
1144 > No links are displayed on the "untrusted" error page.
1151 > The value of this option only matters if the experimental trust mechanism has been
1153 HREF="config.html#TRUSTFILE"
1164 > If you use the trust mechanism, it is a good idea to write up some on-line
1165 documentation about your trust policy and to specify the URL(s) here.
1166 Use multiple times for multiple URLs.
1169 > The URL(s) should be added to the trustfile as well, so users don't end up
1170 locked out from the information on why they were locked out in the first place!
1181 NAME="ADMIN-ADDRESS"
1183 >7.2.3. admin-address</H4
1187 CLASS="VARIABLELIST"
1193 > An email address to reach the proxy administrator.
1215 >Effect if unset:</DT
1218 > No email address is displayed on error pages and the CGI user interface.
1232 are unset, the whole "Local Privoxy Support" box on all generated pages will
1244 NAME="PROXY-INFO-URL"
1246 >7.2.4. proxy-info-url</H4
1250 CLASS="VARIABLELIST"
1256 > A URL to documentation about the local <SPAN
1260 configuration or policies.
1282 >Effect if unset:</DT
1285 > No link to local documentation is displayed on error pages and the CGI user interface.
1299 are unset, the whole "Local Privoxy Support" box on all generated pages will
1303 > This URL shouldn't be blocked ;-)
1319 > These options are mainly useful when tracing a problem.
1320 Note that you might also want to invoke
1328 command line option when debugging.
1341 CLASS="VARIABLELIST"
1347 > Key values that determine what information gets logged to the
1349 HREF="config.html#LOGFILE"
1370 >12289 (i.e.: URLs plus informational and warning messages)</P
1373 >Effect if unset:</DT
1376 > Nothing gets logged.
1383 > The available debug levels are:
1393 CLASS="PROGRAMLISTING"
1394 > debug 1 # show each GET/POST/CONNECT request
1395 debug 2 # show each connection status
1396 debug 4 # show I/O status
1397 debug 8 # show header parsing
1398 debug 16 # log all data into the logfile
1399 debug 32 # debug force feature
1400 debug 64 # debug regular expression filter
1401 debug 128 # debug fast redirects
1402 debug 256 # debug GIF de-animation
1403 debug 512 # Common Log Format
1404 debug 1024 # debug kill pop-ups
1405 debug 2048 # CGI user interface
1406 debug 4096 # Startup banner and warnings.
1407 debug 8192 # Non-fatal errors</PRE
1414 > To select multiple debug levels, you can either add them or use
1421 > A debug level of 1 is informative because it will show you each request
1422 as it happens. <SPAN
1426 >1, 4096 and 8192 are highly recommended</I
1429 so that you will notice when things go wrong. The other levels are probably
1430 only of interest if you are hunting down a specific problem. They can produce
1431 a hell of an output (especially 16).
1435 > The reporting of <SPAN
1441 > errors (i.e. ones which crash
1445 >) is always on and cannot be disabled.
1448 > If you want to use CLF (Common Log Format), you should set <SPAN
1458 > and not enable anything else.
1469 NAME="SINGLE-THREADED"
1471 >7.3.2. single-threaded</H4
1475 CLASS="VARIABLELIST"
1481 > Whether to run only one server thread
1509 >Effect if unset:</DT
1512 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1513 serve multiple requests simultaneously.
1520 > This option is only there for debug purposes and you should never
1521 need to use it. <SPAN
1525 >It will drastically reduce performance.</I
1539 NAME="ACCESS-CONTROL"
1541 >7.4. Access Control and Security</H2
1543 > This section of the config file controls the security-relevant aspects
1554 NAME="LISTEN-ADDRESS"
1556 >7.4.1. listen-address</H4
1560 CLASS="VARIABLELIST"
1566 > The IP address and TCP port on which <SPAN
1570 listen for client requests.
1596 >Effect if unset:</DT
1599 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1600 home users who run <SPAN
1603 > on the same machine as
1611 > You will need to configure your browser(s) to this proxy address and port.
1614 > If you already have another service running on port 8118, or if you want to
1615 serve requests from other machines (e.g. on your local network) as well, you
1616 will need to override the default.
1619 > If you leave out the IP address, <SPAN
1623 bind to all interfaces (addresses) on your machine and may become reachable
1624 from the Internet. In that case, consider using <A
1625 HREF="config.html#ACLS"
1626 >access control lists</A
1627 > (ACL's, see below), and/or
1634 > to untrusted users, you will
1635 also want to turn off the <TT
1638 HREF="config.html#ENABLE-EDIT-ACTIONS"
1639 >enable-edit-actions</A
1645 HREF="config.html#ENABLE-REMOTE-TOGGLE"
1646 >enable-remote-toggle</A
1656 > Suppose you are running <SPAN
1660 a machine which has the address 192.168.0.1 on your local private network
1661 (192.168.0.0) and has another outside connection with a different address.
1662 You want it to serve requests from inside only:
1672 CLASS="PROGRAMLISTING"
1673 > listen-address 192.168.0.1:8118</PRE
1694 CLASS="VARIABLELIST"
1700 > Initial state of "toggle" status
1716 >Effect if unset:</DT
1719 > Act as if toggled on
1726 > If set to 0, <SPAN
1732 >"toggled off"</SPAN
1733 > mode, i.e. behave like a normal, content-neutral
1734 proxy where all ad blocking, filtering, etc are disabled. See
1737 >enable-remote-toggle</TT
1738 > below. This is not really useful
1739 anymore, since toggling is much easier via <A
1740 HREF="http://config.privoxy.org/toggle"
1742 >the web interface</A
1750 > The windows version will only display the toggle icon in the system tray
1751 if this option is present.
1762 NAME="ENABLE-REMOTE-TOGGLE"
1764 >7.4.3. enable-remote-toggle</H4
1768 CLASS="VARIABLELIST"
1774 > Whether or not the <A
1775 HREF="http://config.privoxy.org/toggle"
1795 >Effect if unset:</DT
1798 > The web-based toggle feature is disabled.
1805 > When toggled off, <SPAN
1808 > acts like a normal,
1809 content-neutral proxy, i.e. it acts as if none of the actions applied to
1813 > For the time being, access to the toggle feature can <SPAN
1820 controlled separately by <SPAN
1823 > or HTTP authentication,
1824 so that everybody who can access <SPAN
1835 toggle it for all users. So this option is <SPAN
1842 for multi-user environments with untrusted users.
1845 > Note that you must have compiled <SPAN
1849 support for this feature, otherwise this option has no effect.
1860 NAME="ENABLE-EDIT-ACTIONS"
1862 >7.4.4. enable-edit-actions</H4
1866 CLASS="VARIABLELIST"
1872 > Whether or not the <A
1873 HREF="http://config.privoxy.org/show-status"
1893 >Effect if unset:</DT
1896 > The web-based actions file editor is disabled.
1903 > For the time being, access to the editor can <SPAN
1910 controlled separately by <SPAN
1913 > or HTTP authentication,
1914 so that everybody who can access <SPAN
1925 modify its configuration for all users. So this option is <SPAN
1932 > for multi-user environments with untrusted users.
1935 > Note that you must have compiled <SPAN
1939 support for this feature, otherwise this option has no effect.
1952 >7.4.5. ACLs: permit-access and deny-access</H4
1954 NAME="PERMIT-ACCESS"
1962 CLASS="VARIABLELIST"
1968 > Who can access what.
2010 > are IP addresses in dotted decimal notation or valid
2022 > are subnet masks in CIDR notation, i.e. integer
2023 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
2024 destination part are optional.
2040 >Effect if unset:</DT
2043 > Don't restrict access further than implied by <TT
2053 > Access controls are included at the request of ISPs and systems
2054 administrators, and <SPAN
2058 >are not usually needed by individual users</I
2061 For a typical home user, it will normally suffice to ensure that
2065 > only listens on the localhost
2066 (127.0.0.1) or internal (home) network address by means of the
2068 HREF="config.html#LISTEN-ADDRESS"
2080 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
2081 for a firewall or to encourage anyone to defer addressing basic security
2085 > Multiple ACL lines are OK.
2086 If any ACLs are specified, then the <SPAN
2090 talks only to IP addresses that match at least one <TT
2094 and don't match any subsequent <TT
2097 > line. In other words, the
2098 last match wins, with the default being <TT
2107 > is using a forwarder (see <TT
2111 for a particular destination URL, the <TT
2117 that is examined is the address of the forwarder and <SPAN
2124 of the ultimate target. This is necessary because it may be impossible for the local
2128 > to determine the IP address of the
2129 ultimate target (that's often what gateways are used for).
2132 > You should prefer using IP addresses over DNS names, because the address lookups take
2133 time. All DNS names must resolve! You can <SPAN
2139 > use domain patterns
2143 > or partial domain names. If a DNS name resolves to multiple
2144 IP addresses, only the first one is used.
2147 > Denying access to particular sites by ACL may have undesired side effects
2148 if the site in question is hosted on a machine which also hosts other sites.
2155 > Explicitly define the default behavior if no ACL and
2163 is OK. The absence of a <TT
2175 > destination addresses are OK:
2186 > permit-access localhost</PRE
2193 > Allow any host on the same class C subnet as www.privoxy.org access to
2194 nothing but www.example.com:
2205 > permit-access www.privoxy.org/24 www.example.com/32</PRE
2212 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
2213 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
2224 > permit-access 192.168.45.64/26
2225 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2242 >7.4.6. buffer-limit</H4
2246 CLASS="VARIABLELIST"
2252 > Maximum size of the buffer for content filtering.
2268 >Effect if unset:</DT
2271 > Use a 4MB (4096 KB) limit.
2278 > For content filtering, i.e. the <TT
2285 > actions, it is necessary that
2289 > buffers the entire document body.
2290 This can be potentially dangerous, since a server could just keep sending
2291 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2295 > When a document buffer size reaches the <TT
2299 flushed to the client unfiltered and no further attempt to
2300 filter the rest of the document is made. Remember that there may be multiple threads
2301 running, which might require up to <TT
2311 >, unless you have enabled <SPAN
2313 >"single-threaded"</SPAN
2329 >7.5. Forwarding</H2
2331 > This feature allows routing of HTTP requests through a chain of
2333 It can be used to better protect privacy and confidentiality when
2334 accessing specific domains by routing requests to those domains
2335 through an anonymous public proxy (see e.g. <A
2336 HREF="http://www.multiproxy.org/anon_list.htm"
2338 >http://www.multiproxy.org/anon_list.htm</A
2340 Or to use a caching proxy to speed up browsing. Or chaining to a parent
2341 proxy may be necessary because the machine that <SPAN
2345 runs on has no direct Internet access.</P
2347 > Also specified here are SOCKS proxies. <SPAN
2351 supports the SOCKS 4 and SOCKS 4A protocols.</P
2363 CLASS="VARIABLELIST"
2369 > To which parent HTTP proxy specific requests should be routed.
2401 HREF="actions-file.html#AF-PATTERNS"
2404 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2423 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
2424 optionally followed by its listening port (default: 8080).
2425 Use a single dot (<TT
2430 >"no forwarding"</SPAN
2447 >Effect if unset:</DT
2450 > Don't use parent HTTP proxies.
2465 >, then requests are not
2466 forwarded to another HTTP proxy but are made directly to the web servers.
2469 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2476 > Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
2487 > forward / anon-proxy.example.org:8080
2495 > Everything goes to our example ISP's caching proxy, except for requests
2496 to that ISP's sites:
2507 > forward / caching-proxy.example-isp.net:8000
2508 forward .example-isp.net .</PRE
2525 >7.5.2. forward-socks4 and forward-socks4a</H4
2527 NAME="FORWARD-SOCKS4"
2530 NAME="FORWARD-SOCKS4A"
2535 CLASS="VARIABLELIST"
2541 > Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
2584 HREF="actions-file.html#AF-PATTERNS"
2587 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2606 are IP addresses in dotted decimal notation or valid DNS names (<TT
2617 >"no HTTP forwarding"</SPAN
2618 >), and the optional
2624 > parameters are TCP ports, i.e. integer values from 1 to 64535
2640 >Effect if unset:</DT
2643 > Don't use SOCKS proxies.
2650 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2653 > The difference between <TT
2658 >forward-socks4a</TT
2660 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2661 server, while in SOCKS 4 it happens locally.
2672 >, then requests are not
2673 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2681 > From the company example.com, direct connections are made to all
2685 > domains, but everything outbound goes through
2686 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2698 > forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
2699 forward .example.com .</PRE
2706 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2717 > forward-socks4 / socks-gw.example.com:1080 .</PRE
2732 NAME="ADVANCED-FORWARDING-EXAMPLES"
2734 >7.5.3. Advanced Forwarding Examples</H4
2736 > If you have links to multiple ISPs that provide various special content
2737 only to their subscribers, you can configure multiple <SPAN
2741 which have connections to the respective ISPs to act as forwarders to each other, so that
2748 > users can see the internal content of all ISPs.</P
2750 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2751 isp-b.net. Both run <SPAN
2755 configuration can look like this:</P
2768 forward .isp-b.net host-b:8118</PRE
2785 forward .isp-a.net host-a:8118</PRE
2791 > Now, your users can set their browser's proxy to use either
2792 host-a or host-b and be able to browse the internal content
2793 of both isp-a and isp-b.</P
2795 > If you intend to chain <SPAN
2802 > locally, then chain as
2805 >browser -> squid -> privoxy</TT
2806 > is the recommended way. </P
2808 > Assuming that <SPAN
2815 run on the same box, your <SPAN
2818 > configuration could then look like this:</P
2828 > # Define Privoxy as parent proxy (without ICP)
2829 cache_peer 127.0.0.1 parent 8118 7 no-query
2831 # Define ACL for protocol FTP
2834 # Do not forward FTP requests to Privoxy
2835 always_direct allow ftp
2837 # Forward all the rest to Privoxy
2838 never_direct allow all</PRE
2844 > You would then need to change your browser's proxy settings to <SPAN
2847 >'s address and port.
2848 Squid normally uses port 3128. If unsure consult <TT
2856 > You could just as well decide to only forward requests for Windows executables through
2857 a virus-scanning parent proxy, say, on <TT
2859 >antivir.example.com</TT
2871 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</PRE
2885 >7.6. Windows GUI Options</H2
2890 > has a number of options specific to the
2891 Windows GUI interface:</P
2893 NAME="ACTIVITY-ANIMATION"
2898 >"activity-animation"</SPAN
2903 > icon will animate when
2907 > is active. To turn off, set to 0.</P
2912 CLASS="LITERALLAYOUT"
2917 >activity-animation 1</I
2920 </P
2930 >"log-messages"</SPAN
2935 > will log messages to the console
2941 CLASS="LITERALLAYOUT"
2949 </P
2954 NAME="LOG-BUFFER-SIZE"
2960 >"log-buffer-size"</SPAN
2961 > is set to 1, the size of the log buffer,
2962 i.e. the amount of memory used for the log messages displayed in the
2963 console window, will be limited to <SPAN
2965 >"log-max-lines"</SPAN
2968 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
2969 eat up all your memory!</P
2974 CLASS="LITERALLAYOUT"
2979 >log-buffer-size 1</I
2982 </P
2987 NAME="LOG-MAX-LINES"
2992 >log-max-lines</SPAN
2993 > is the maximum number of lines held
2994 in the log buffer. See above.</P
2999 CLASS="LITERALLAYOUT"
3004 >log-max-lines 200</I
3007 </P
3012 NAME="LOG-HIGHLIGHT-MESSAGES"
3017 >"log-highlight-messages"</SPAN
3022 > will highlight portions of the log
3023 messages with a bold-faced font:</P
3028 CLASS="LITERALLAYOUT"
3033 >log-highlight-messages 1</I
3036 </P
3041 NAME="LOG-FONT-NAME"
3044 > The font used in the console window:</P
3049 CLASS="LITERALLAYOUT"
3054 >log-font-name Comic Sans MS</I
3057 </P
3062 NAME="LOG-FONT-SIZE"
3065 > Font size used in the console window:</P
3070 CLASS="LITERALLAYOUT"
3078 </P
3083 NAME="SHOW-ON-TASK-BAR"
3089 >"show-on-task-bar"</SPAN
3090 > controls whether or not
3094 > will appear as a button on the Task bar
3100 CLASS="LITERALLAYOUT"
3105 >show-on-task-bar 0</I
3108 </P
3113 NAME="CLOSE-BUTTON-MINIMIZES"
3118 >"close-button-minimizes"</SPAN
3119 > is set to 1, the Windows close
3120 button will minimize <SPAN
3123 > instead of closing
3124 the program (close with the exit option on the File menu).</P
3129 CLASS="LITERALLAYOUT"
3134 >close-button-minimizes 1</I
3137 </P
3147 >"hide-console"</SPAN
3148 > option is specific to the MS-Win console
3152 >. If this option is used,
3156 > will disconnect from and hide the
3162 CLASS="LITERALLAYOUT"
3170 </P
3181 SUMMARY="Footer navigation table"
3192 HREF="configuration.html"
3210 HREF="actions-file.html"