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.
518 HREF="filter-file.html"
520 > contains content modification
522 HREF="appendix.html#REGEX"
523 >regular expressions</A
524 >. These rules permit
525 powerful changes on the content of Web pages, e.g., you could disable your favorite
526 JavaScript annoyances, re-write the actual displayed text, or just have some
534 it appears on a Web page.
541 HREF="actions-file.html#FILTER"
550 actions rely on the relevant filter (<TT
556 to be defined in the filter file!
559 > A pre-defined filter file called <TT
563 a bunch of handy filters for common problems is included in the distribution.
564 See the section on the <TT
567 HREF="actions-file.html#FILTER"
594 > The log file to use
601 >File name, relative to <TT
610 >logfile (Unix) <SPAN
616 > privoxy.log (Windows)</P
619 >Effect if unset:</DT
622 > No log file is used, all log messages go to the console (<TT
632 > The logfile is where all logging and error messages are written. The level
633 of detail and number of messages are set with the <TT
637 option (see below). The logfile can be useful for tracking down a problem with
641 > (e.g., it's not blocking an ad you
642 think it should block) but in most cases you probably will never look at it.
645 > Your logfile will grow indefinitely, and you will probably want to
646 periodically remove it. On Unix systems, you can do this with a cron job
650 >). For Red Hat, a <B
654 script has been included.
657 > On SuSE Linux systems, you can place a line like <SPAN
660 +1024k 644 nobody.nogroup"</SPAN
665 the effect that cron.daily will automatically archive, gzip, and empty the
666 log, when it exceeds 1M size.
669 > Any log files must be writable by whatever user <SPAN
673 is being run as (default on UNIX, user id is <SPAN
699 > The file to store intercepted cookies in
706 >File name, relative to <TT
715 >jarfile (Unix) <SPAN
721 > privoxy.jar (Windows)</P
724 >Effect if unset:</DT
727 > Intercepted cookies are not stored at all.
734 > The jarfile may grow to ridiculous sizes over time.
747 >7.1.7. trustfile</H4
757 > The trust file to use
764 >File name, relative to <TT
777 >Unset (commented out)</I
779 >. When activated: trust (Unix) <SPAN
785 > trust.txt (Windows)</P
788 >Effect if unset:</DT
791 > The entire trust mechanism is turned off.
798 > The trust mechanism is an experimental feature for building white-lists and should
799 be used with care. It is <SPAN
805 > recommended for the casual user.
808 > If you specify a trust file, <SPAN
812 access to sites that are specified in the trustfile. Sites can be listed
819 > character limits access to this site
820 only (and any sub-paths within this site), e.g.
823 >~www.example.com</TT
827 > Or, you can designate sites as <SPAN
831 >trusted referrers</I
834 prepending the name with a <TT
837 > character. The effect is that
838 access to untrusted sites will be granted -- but only if a link from this
839 trusted referrer was used. The link target will then be added to the
843 > so that future, direct accesses will be granted.
844 Sites added via this mechanism do not become trusted referrers themselves
845 (i.e. they are added with a <TT
854 > operator in the trust file, it may grow
855 considerably over time.
858 > It is recommended that <SPAN
867 >--disable-toggle</TT
871 > --disable-editor</TT
872 > options, if this feature is to be
876 > Possible applications include limiting Internet access for children.
890 >7.2. Local Set-up Documentation</H2
892 > If you intend to operate <SPAN
896 than just yourself, it might be a good idea to let them know how to reach
897 you, what you block and why you do that, your policies, etc.
906 >7.2.1. user-manual</H4
916 > Location of the <SPAN
926 >A fully qualified URI</P
941 >Effect if unset:</DT
945 HREF="http://www.privoxy.org/user-manual/"
947 >http://www.privoxy.org/<TT
954 will be used, where <TT
969 > The User Manual URI is used for help links from some of the internal CGI pages.
970 The manual itself is normally packaged with the binary distributions, so you probably want
971 to set this to a locally installed copy. For multi-user setups, you could provide a copy on
972 a local webserver for all your users and use the corresponding URL here.
978 > Unix, in local filesystem:
989 >  user-manual  file:///usr/share/doc/privoxy-3.0.4/user-manual/</PRE
996 > Windows, in local filesystem, <SPAN
1002 > use forward slash notation:
1013 >  user-manual  file:/c:/some-dir/privoxy-3.0.4/user-manual/</PRE
1020 > Windows, UNC notation (with forward slashes):
1031 >  user-manual  file://///some-server/some-path/privoxy-3.0.4/user-manual/</PRE
1038 > Any platform, on local webserver (called <SPAN
1040 >"local-webserver"</SPAN
1052 >  user-manual  http://local-webserver/privoxy-user-manual/</PRE
1077 > If set, this option should be <SPAN
1081 >the first option in the config
1084 >, because it is used while the config file is being read.
1099 NAME="TRUST-INFO-URL"
1101 >7.2.2. trust-info-url</H4
1105 CLASS="VARIABLELIST"
1111 > A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
1124 >Two example URL are provided</P
1127 >Effect if unset:</DT
1130 > No links are displayed on the "untrusted" error page.
1137 > The value of this option only matters if the experimental trust mechanism has been
1139 HREF="config.html#TRUSTFILE"
1150 > If you use the trust mechanism, it is a good idea to write up some on-line
1151 documentation about your trust policy and to specify the URL(s) here.
1152 Use multiple times for multiple URLs.
1155 > The URL(s) should be added to the trustfile as well, so users don't end up
1156 locked out from the information on why they were locked out in the first place!
1167 NAME="ADMIN-ADDRESS"
1169 >7.2.3. admin-address</H4
1173 CLASS="VARIABLELIST"
1179 > An email address to reach the proxy administrator.
1201 >Effect if unset:</DT
1204 > No email address is displayed on error pages and the CGI user interface.
1218 are unset, the whole "Local Privoxy Support" box on all generated pages will
1230 NAME="PROXY-INFO-URL"
1232 >7.2.4. proxy-info-url</H4
1236 CLASS="VARIABLELIST"
1242 > A URL to documentation about the local <SPAN
1246 configuration or policies.
1268 >Effect if unset:</DT
1271 > No link to local documentation is displayed on error pages and the CGI user interface.
1285 are unset, the whole "Local Privoxy Support" box on all generated pages will
1289 > This URL shouldn't be blocked ;-)
1305 > These options are mainly useful when tracing a problem.
1306 Note that you might also want to invoke
1314 command line option when debugging.
1327 CLASS="VARIABLELIST"
1333 > Key values that determine what information gets logged to the
1335 HREF="config.html#LOGFILE"
1356 >12289 (i.e.: URLs plus informational and warning messages)</P
1359 >Effect if unset:</DT
1362 > Nothing gets logged.
1369 > The available debug levels are:
1379 CLASS="PROGRAMLISTING"
1380 > debug 1 # show each GET/POST/CONNECT request
1381 debug 2 # show each connection status
1382 debug 4 # show I/O status
1383 debug 8 # show header parsing
1384 debug 16 # log all data into the logfile
1385 debug 32 # debug force feature
1386 debug 64 # debug regular expression filter
1387 debug 128 # debug fast redirects
1388 debug 256 # debug GIF de-animation
1389 debug 512 # Common Log Format
1390 debug 1024 # debug kill pop-ups
1391 debug 2048 # CGI user interface
1392 debug 4096 # Startup banner and warnings.
1393 debug 8192 # Non-fatal errors</PRE
1400 > To select multiple debug levels, you can either add them or use
1407 > A debug level of 1 is informative because it will show you each request
1408 as it happens. <SPAN
1412 >1, 4096 and 8192 are highly recommended</I
1415 so that you will notice when things go wrong. The other levels are probably
1416 only of interest if you are hunting down a specific problem. They can produce
1417 a hell of an output (especially 16).
1421 > The reporting of <SPAN
1427 > errors (i.e. ones which crash
1431 >) is always on and cannot be disabled.
1434 > If you want to use CLF (Common Log Format), you should set <SPAN
1444 > and not enable anything else.
1455 NAME="SINGLE-THREADED"
1457 >7.3.2. single-threaded</H4
1461 CLASS="VARIABLELIST"
1467 > Whether to run only one server thread
1495 >Effect if unset:</DT
1498 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1499 serve multiple requests simultaneously.
1506 > This option is only there for debug purposes and you should never
1507 need to use it. <SPAN
1511 >It will drastically reduce performance.</I
1525 NAME="ACCESS-CONTROL"
1527 >7.4. Access Control and Security</H2
1529 > This section of the config file controls the security-relevant aspects
1540 NAME="LISTEN-ADDRESS"
1542 >7.4.1. listen-address</H4
1546 CLASS="VARIABLELIST"
1552 > The IP address and TCP port on which <SPAN
1556 listen for client requests.
1582 >Effect if unset:</DT
1585 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1586 home users who run <SPAN
1589 > on the same machine as
1597 > You will need to configure your browser(s) to this proxy address and port.
1600 > If you already have another service running on port 8118, or if you want to
1601 serve requests from other machines (e.g. on your local network) as well, you
1602 will need to override the default.
1605 > If you leave out the IP address, <SPAN
1609 bind to all interfaces (addresses) on your machine and may become reachable
1610 from the Internet. In that case, consider using <A
1611 HREF="config.html#ACLS"
1612 >access control lists</A
1613 > (ACL's, see below), and/or
1620 > to untrusted users, you will
1621 also want to turn off the <TT
1624 HREF="config.html#ENABLE-EDIT-ACTIONS"
1625 >enable-edit-actions</A
1631 HREF="config.html#ENABLE-REMOTE-TOGGLE"
1632 >enable-remote-toggle</A
1642 > Suppose you are running <SPAN
1646 a machine which has the address 192.168.0.1 on your local private network
1647 (192.168.0.0) and has another outside connection with a different address.
1648 You want it to serve requests from inside only:
1658 CLASS="PROGRAMLISTING"
1659 > listen-address 192.168.0.1:8118</PRE
1680 CLASS="VARIABLELIST"
1686 > Initial state of "toggle" status
1702 >Effect if unset:</DT
1705 > Act as if toggled on
1712 > If set to 0, <SPAN
1718 >"toggled off"</SPAN
1719 > mode, i.e. behave like a normal, content-neutral
1720 proxy where all ad blocking, filtering, etc are disabled. See
1723 >enable-remote-toggle</TT
1724 > below. This is not really useful
1725 anymore, since toggling is much easier via <A
1726 HREF="http://config.privoxy.org/toggle"
1728 >the web interface</A
1736 > The windows version will only display the toggle icon in the system tray
1737 if this option is present.
1748 NAME="ENABLE-REMOTE-TOGGLE"
1750 >7.4.3. enable-remote-toggle</H4
1754 CLASS="VARIABLELIST"
1760 > Whether or not the <A
1761 HREF="http://config.privoxy.org/toggle"
1781 >Effect if unset:</DT
1784 > The web-based toggle feature is disabled.
1791 > When toggled off, <SPAN
1794 > acts like a normal,
1795 content-neutral proxy, i.e. it acts as if none of the actions applied to
1799 > For the time being, access to the toggle feature can <SPAN
1806 controlled separately by <SPAN
1809 > or HTTP authentication,
1810 so that everybody who can access <SPAN
1821 toggle it for all users. So this option is <SPAN
1828 for multi-user environments with untrusted users.
1831 > Note that you must have compiled <SPAN
1835 support for this feature, otherwise this option has no effect.
1846 NAME="ENABLE-EDIT-ACTIONS"
1848 >7.4.4. enable-edit-actions</H4
1852 CLASS="VARIABLELIST"
1858 > Whether or not the <A
1859 HREF="http://config.privoxy.org/show-status"
1879 >Effect if unset:</DT
1882 > The web-based actions file editor is disabled.
1889 > For the time being, access to the editor can <SPAN
1896 controlled separately by <SPAN
1899 > or HTTP authentication,
1900 so that everybody who can access <SPAN
1911 modify its configuration for all users. So this option is <SPAN
1918 > for multi-user environments with untrusted users.
1921 > Note that you must have compiled <SPAN
1925 support for this feature, otherwise this option has no effect.
1938 >7.4.5. ACLs: permit-access and deny-access</H4
1940 NAME="PERMIT-ACCESS"
1948 CLASS="VARIABLELIST"
1954 > Who can access what.
1996 > are IP addresses in dotted decimal notation or valid
2008 > are subnet masks in CIDR notation, i.e. integer
2009 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
2010 destination part are optional.
2026 >Effect if unset:</DT
2029 > Don't restrict access further than implied by <TT
2039 > Access controls are included at the request of ISPs and systems
2040 administrators, and <SPAN
2044 >are not usually needed by individual users</I
2047 For a typical home user, it will normally suffice to ensure that
2051 > only listens on the localhost
2052 (127.0.0.1) or internal (home) network address by means of the
2054 HREF="config.html#LISTEN-ADDRESS"
2066 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
2067 for a firewall or to encourage anyone to defer addressing basic security
2071 > Multiple ACL lines are OK.
2072 If any ACLs are specified, then the <SPAN
2076 talks only to IP addresses that match at least one <TT
2080 and don't match any subsequent <TT
2083 > line. In other words, the
2084 last match wins, with the default being <TT
2093 > is using a forwarder (see <TT
2097 for a particular destination URL, the <TT
2103 that is examined is the address of the forwarder and <SPAN
2110 of the ultimate target. This is necessary because it may be impossible for the local
2114 > to determine the IP address of the
2115 ultimate target (that's often what gateways are used for).
2118 > You should prefer using IP addresses over DNS names, because the address lookups take
2119 time. All DNS names must resolve! You can <SPAN
2125 > use domain patterns
2129 > or partial domain names. If a DNS name resolves to multiple
2130 IP addresses, only the first one is used.
2133 > Denying access to particular sites by ACL may have undesired side effects
2134 if the site in question is hosted on a machine which also hosts other sites.
2141 > Explicitly define the default behavior if no ACL and
2149 is OK. The absence of a <TT
2161 > destination addresses are OK:
2172 > permit-access localhost</PRE
2179 > Allow any host on the same class C subnet as www.privoxy.org access to
2180 nothing but www.example.com:
2191 > permit-access www.privoxy.org/24 www.example.com/32</PRE
2198 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
2199 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
2210 > permit-access 192.168.45.64/26
2211 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2228 >7.4.6. buffer-limit</H4
2232 CLASS="VARIABLELIST"
2238 > Maximum size of the buffer for content filtering.
2254 >Effect if unset:</DT
2257 > Use a 4MB (4096 KB) limit.
2264 > For content filtering, i.e. the <TT
2271 > actions, it is necessary that
2275 > buffers the entire document body.
2276 This can be potentially dangerous, since a server could just keep sending
2277 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2281 > When a document buffer size reaches the <TT
2285 flushed to the client unfiltered and no further attempt to
2286 filter the rest of the document is made. Remember that there may be multiple threads
2287 running, which might require up to <TT
2297 >, unless you have enabled <SPAN
2299 >"single-threaded"</SPAN
2315 >7.5. Forwarding</H2
2317 > This feature allows routing of HTTP requests through a chain of
2319 It can be used to better protect privacy and confidentiality when
2320 accessing specific domains by routing requests to those domains
2321 through an anonymous public proxy (see e.g. <A
2322 HREF="http://www.multiproxy.org/anon_list.htm"
2324 >http://www.multiproxy.org/anon_list.htm</A
2326 Or to use a caching proxy to speed up browsing. Or chaining to a parent
2327 proxy may be necessary because the machine that <SPAN
2331 runs on has no direct Internet access.</P
2333 > Also specified here are SOCKS proxies. <SPAN
2337 supports the SOCKS 4 and SOCKS 4A protocols.</P
2349 CLASS="VARIABLELIST"
2355 > To which parent HTTP proxy specific requests should be routed.
2387 HREF="actions-file.html#AF-PATTERNS"
2390 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2409 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
2410 optionally followed by its listening port (default: 8080).
2411 Use a single dot (<TT
2416 >"no forwarding"</SPAN
2433 >Effect if unset:</DT
2436 > Don't use parent HTTP proxies.
2451 >, then requests are not
2452 forwarded to another HTTP proxy but are made directly to the web servers.
2455 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2462 > Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
2473 > forward / anon-proxy.example.org:8080
2481 > Everything goes to our example ISP's caching proxy, except for requests
2482 to that ISP's sites:
2493 > forward / caching-proxy.example-isp.net:8000
2494 forward .example-isp.net .</PRE
2511 >7.5.2. forward-socks4 and forward-socks4a</H4
2513 NAME="FORWARD-SOCKS4"
2516 NAME="FORWARD-SOCKS4A"
2521 CLASS="VARIABLELIST"
2527 > Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
2570 HREF="actions-file.html#AF-PATTERNS"
2573 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2592 are IP addresses in dotted decimal notation or valid DNS names (<TT
2603 >"no HTTP forwarding"</SPAN
2604 >), and the optional
2610 > parameters are TCP ports, i.e. integer values from 1 to 64535
2626 >Effect if unset:</DT
2629 > Don't use SOCKS proxies.
2636 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2639 > The difference between <TT
2644 >forward-socks4a</TT
2646 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2647 server, while in SOCKS 4 it happens locally.
2658 >, then requests are not
2659 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2667 > From the company example.com, direct connections are made to all
2671 > domains, but everything outbound goes through
2672 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2684 > forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
2685 forward .example.com .</PRE
2692 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2703 > forward-socks4 / socks-gw.example.com:1080 .</PRE
2718 NAME="ADVANCED-FORWARDING-EXAMPLES"
2720 >7.5.3. Advanced Forwarding Examples</H4
2722 > If you have links to multiple ISPs that provide various special content
2723 only to their subscribers, you can configure multiple <SPAN
2727 which have connections to the respective ISPs to act as forwarders to each other, so that
2734 > users can see the internal content of all ISPs.</P
2736 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2737 isp-b.net. Both run <SPAN
2741 configuration can look like this:</P
2754 forward .isp-b.net host-b:8118</PRE
2771 forward .isp-a.net host-a:8118</PRE
2777 > Now, your users can set their browser's proxy to use either
2778 host-a or host-b and be able to browse the internal content
2779 of both isp-a and isp-b.</P
2781 > If you intend to chain <SPAN
2788 > locally, then chain as
2791 >browser -> squid -> privoxy</TT
2792 > is the recommended way. </P
2794 > Assuming that <SPAN
2801 run on the same box, your <SPAN
2804 > configuration could then look like this:</P
2814 > # Define Privoxy as parent proxy (without ICP)
2815 cache_peer 127.0.0.1 parent 8118 7 no-query
2817 # Define ACL for protocol FTP
2820 # Do not forward FTP requests to Privoxy
2821 always_direct allow ftp
2823 # Forward all the rest to Privoxy
2824 never_direct allow all</PRE
2830 > You would then need to change your browser's proxy settings to <SPAN
2833 >'s address and port.
2834 Squid normally uses port 3128. If unsure consult <TT
2842 > You could just as well decide to only forward requests for Windows executables through
2843 a virus-scanning parent proxy, say, on <TT
2845 >antivir.example.com</TT
2857 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</PRE
2871 >7.6. Windows GUI Options</H2
2876 > has a number of options specific to the
2877 Windows GUI interface:</P
2879 NAME="ACTIVITY-ANIMATION"
2884 >"activity-animation"</SPAN
2889 > icon will animate when
2893 > is active. To turn off, set to 0.</P
2898 CLASS="LITERALLAYOUT"
2903 >activity-animation 1</I
2906 </P
2916 >"log-messages"</SPAN
2921 > will log messages to the console
2927 CLASS="LITERALLAYOUT"
2935 </P
2940 NAME="LOG-BUFFER-SIZE"
2946 >"log-buffer-size"</SPAN
2947 > is set to 1, the size of the log buffer,
2948 i.e. the amount of memory used for the log messages displayed in the
2949 console window, will be limited to <SPAN
2951 >"log-max-lines"</SPAN
2954 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
2955 eat up all your memory!</P
2960 CLASS="LITERALLAYOUT"
2965 >log-buffer-size 1</I
2968 </P
2973 NAME="LOG-MAX-LINES"
2978 >log-max-lines</SPAN
2979 > is the maximum number of lines held
2980 in the log buffer. See above.</P
2985 CLASS="LITERALLAYOUT"
2990 >log-max-lines 200</I
2993 </P
2998 NAME="LOG-HIGHLIGHT-MESSAGES"
3003 >"log-highlight-messages"</SPAN
3008 > will highlight portions of the log
3009 messages with a bold-faced font:</P
3014 CLASS="LITERALLAYOUT"
3019 >log-highlight-messages 1</I
3022 </P
3027 NAME="LOG-FONT-NAME"
3030 > The font used in the console window:</P
3035 CLASS="LITERALLAYOUT"
3040 >log-font-name Comic Sans MS</I
3043 </P
3048 NAME="LOG-FONT-SIZE"
3051 > Font size used in the console window:</P
3056 CLASS="LITERALLAYOUT"
3064 </P
3069 NAME="SHOW-ON-TASK-BAR"
3075 >"show-on-task-bar"</SPAN
3076 > controls whether or not
3080 > will appear as a button on the Task bar
3086 CLASS="LITERALLAYOUT"
3091 >show-on-task-bar 0</I
3094 </P
3099 NAME="CLOSE-BUTTON-MINIMIZES"
3104 >"close-button-minimizes"</SPAN
3105 > is set to 1, the Windows close
3106 button will minimize <SPAN
3109 > instead of closing
3110 the program (close with the exit option on the File menu).</P
3115 CLASS="LITERALLAYOUT"
3120 >close-button-minimizes 1</I
3123 </P
3133 >"hide-console"</SPAN
3134 > option is specific to the MS-Win console
3138 >. If this option is used,
3142 > will disconnect from and hide the
3148 CLASS="LITERALLAYOUT"
3156 </P
3167 SUMMARY="Footer navigation table"
3178 HREF="configuration.html"
3196 HREF="actions-file.html"