4 >The Main Configuration File</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 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 User Manual</TH
48 HREF="configuration.html"
62 HREF="actions-file.html"
76 NAME="CONFIG">7. The Main Configuration File</H1
78 > Again, the main configuration file is named <TT
82 Linux/Unix/BSD and OS/2, and <TT
86 Configuration lines consist of an initial keyword followed by a list of
87 values, all separated by whitespace (any number of spaces or tabs). For
98 >confdir /etc/privoxy</I
105 > Assigns the value <TT
112 > and thus indicates that the configuration
113 directory is named <SPAN
115 >"/etc/privoxy/"</SPAN
118 > All options in the config file except for <TT
125 > are optional. Watch out in the below description
126 for what happens if you leave them unset.</P
128 > The main config file controls all aspects of <SPAN
132 operation that are not location dependent (i.e. they apply universally, no matter
133 where you may be surfing).</P
139 NAME="CONF-LOG-LOC">7.1. Configuration and Log File Locations</H2
144 > can (and normally does) use a number of
145 other files for additional configuration, help and logging.
146 This section of the configuration file tells <SPAN
150 where to find those other files. </P
152 > The user running <SPAN
156 permission for all configuration files, and write permission to any files
157 that would be modified, such as log files and actions files.</P
163 NAME="CONFDIR">7.1.1. confdir</H4
173 >The directory where the other configuration files are located</P
185 >/etc/privoxy (Unix) <SPAN
194 > installation dir (Windows) </P
197 >Effect if unset:</DT
221 > When development goes modular and multi-user, the blocker, filter, and
222 per-user config will be stored in subdirectories of <SPAN
226 For now, the configuration directory structure is flat, except for
229 >confdir/templates</TT
230 >, where the HTML templates for CGI
231 output reside (e.g. <SPAN
245 NAME="LOGDIR">7.1.2. logdir</H4
255 > The directory where all logging takes place (i.e. where <TT
275 >/var/log/privoxy (Unix) <SPAN
284 > installation dir (Windows) </P
287 >Effect if unset:</DT
319 NAME="ACTIONSFILE">7.1.3. actionsfile</H4
321 NAME="DEFAULT.ACTION"
324 NAME="STANDARD.ACTION"
339 HREF="actions-file.html"
348 >File name, relative to <TT
367 CLASS="LITERALLAYOUT"
368 > standard # Internal purposes, no editing recommended</P
375 CLASS="LITERALLAYOUT"
376 > default # Main actions file</P
383 CLASS="LITERALLAYOUT"
384 > user # User customizations</P
394 >Effect if unset:</DT
397 > No actions are taken at all. Simple neutral proxying.
407 > lines are permitted, and are in fact recommended!
411 The default values include standard.action, which is used for internal
412 purposes and should be loaded, default.action, which is the
416 > actions file maintained by the developers, and
420 >, where you can make your personal additions.
424 Actions files are where all the per site and per URL configuration is done for
425 ad blocking, cookie management, privacy considerations, etc.
426 There is no point in using <SPAN
430 least one actions file.
441 NAME="FILTERFILE">7.1.4. filterfile</H4
443 NAME="DEFAULT.FILTER"
455 HREF="filter-file.html"
464 >File name, relative to <TT
473 >default.filter (Unix) <SPAN
479 > default.filter.txt (Windows)</P
482 >Effect if unset:</DT
485 > No textual content filtering takes place, i.e. all
489 HREF="actions-file.html#FILTER"
498 actions in the actions files are turned neutral.
506 HREF="filter-file.html"
508 > contains content modification
510 HREF="appendix.html#REGEX"
511 >regular expressions</A
512 >. These rules permit
513 powerful changes on the content of Web pages, e.g., you could disable your favorite
514 JavaScript annoyances, re-write the actual displayed text, or just have some
522 it appears on a Web page.
529 HREF="actions-file.html#FILTER"
538 actions rely on the relevant filter (<TT
544 to be defined in the filter file!
547 > A pre-defined filter file called <TT
551 a bunch of handy filters for common problems is included in the distribution.
552 See the section on the <TT
555 HREF="actions-file.html#FILTER"
570 NAME="LOGFILE">7.1.5. logfile</H4
580 > The log file to use
587 >File name, relative to <TT
596 >logfile (Unix) <SPAN
602 > privoxy.log (Windows)</P
605 >Effect if unset:</DT
608 > No log file is used, all log messages go to the console (<TT
618 > The windows version will additionally log to the console.
621 > The logfile is where all logging and error messages are written. The level
622 of detail and number of messages are set with the <TT
626 option (see below). The logfile can be useful for tracking down a problem with
630 > (e.g., it's not blocking an ad you
631 think it should block) but in most cases you probably will never look at it.
634 > Your logfile will grow indefinitely, and you will probably want to
635 periodically remove it. On Unix systems, you can do this with a cron job
639 >). For Red Hat, a <B
643 script has been included.
646 > On SuSE Linux systems, you can place a line like <SPAN
649 +1024k 644 nobody.nogroup"</SPAN
654 the effect that cron.daily will automatically archive, gzip, and empty the
655 log, when it exceeds 1M size.
658 > Any log files must be writable by whatever user <SPAN
662 is being run as (default on UNIX, user id is <SPAN
676 NAME="JARFILE">7.1.6. jarfile</H4
686 > The file to store intercepted cookies in
693 >File name, relative to <TT
702 >jarfile (Unix) <SPAN
708 > privoxy.jar (Windows)</P
711 >Effect if unset:</DT
714 > Intercepted cookies are not stored at all.
721 > The jarfile may grow to ridiculous sizes over time.
732 NAME="TRUSTFILE">7.1.7. trustfile</H4
742 > The trust file to use
749 >File name, relative to <TT
762 >Unset (commented out)</I
764 >. When activated: trust (Unix) <SPAN
770 > trust.txt (Windows)</P
773 >Effect if unset:</DT
776 > The whole trust mechanism is turned off.
783 > The trust mechanism is an experimental feature for building white-lists and should
784 be used with care. It is <SPAN
790 > recommended for the casual user.
793 > If you specify a trust file, <SPAN
797 access to sites that are named in the trustfile.
798 You can also mark sites as trusted referrers (with <TT
802 the effect that access to untrusted sites will be granted, if a link from a
803 trusted referrer was used.
804 The link target will then be added to the <SPAN
808 Possible applications include limiting Internet access for children.
814 > operator in the trust file, it may grow considerably over time.
826 NAME="LOCAL-SET-UP">7.2. Local Set-up Documentation</H2
828 > If you intend to operate <SPAN
832 than just yourself, it might be a good idea to let them know how to reach
833 you, what you block and why you do that, your policies, etc.
840 NAME="USER-MANUAL">7.2.1. user-manual</H4
850 > Location of the <SPAN
860 >A fully qualified URI</P
875 >Effect if unset:</DT
879 HREF="http://www.privoxy.org/user-manual/"
881 >http://www.privoxy.org/<TT
888 will be used, where <TT
903 > The User Manual URI is used for help links from some of the internal CGI pages.
904 The manual itself is normally packaged with the binary distributions, so you probably want
905 to set this to a locally installed copy. For multi-user setups, you could provide a copy on
906 a local webserver for all your users and use the corresponding URL here.
912 > Unix, in local filesystem:
923 >user-manual  file:///usr/share/doc/privoxy-2.9.15/user-manual/</PRE
930 > Any platform, on local webserver (called <SPAN
932 >"local-webserver"</SPAN
944 >user-manual  http://local-webserver/privoxy-user-manual/</PRE
969 > If set, this option should be <SPAN
973 >the first option in the config
976 >, because it is used while the config file is being read.
991 NAME="TRUST-INFO-URL">7.2.2. trust-info-url</H4
1001 > A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
1014 >Two example URL are provided</P
1017 >Effect if unset:</DT
1020 > No links are displayed on the "untrusted" error page.
1027 > The value of this option only matters if the experimental trust mechanism has been
1029 HREF="config.html#TRUSTFILE"
1040 > If you use the trust mechanism, it is a good idea to write up some on-line
1041 documentation about your trust policy and to specify the URL(s) here.
1042 Use multiple times for multiple URLs.
1045 > The URL(s) should be added to the trustfile as well, so users don't end up
1046 locked out from the information on why they were locked out in the first place!
1057 NAME="ADMIN-ADDRESS">7.2.3. admin-address</H4
1061 CLASS="VARIABLELIST"
1067 > An email address to reach the proxy administrator.
1089 >Effect if unset:</DT
1092 > No email address is displayed on error pages and the CGI user interface.
1106 are unset, the whole "Local Privoxy Support" box on all generated pages will
1118 NAME="PROXY-INFO-URL">7.2.4. proxy-info-url</H4
1122 CLASS="VARIABLELIST"
1128 > A URL to documentation about the local <SPAN
1132 configuration or policies.
1154 >Effect if unset:</DT
1157 > No link to local documentation is displayed on error pages and the CGI user interface.
1171 are unset, the whole "Local Privoxy Support" box on all generated pages will
1175 > This URL shouldn't be blocked ;-)
1187 NAME="DEBUGGING">7.3. Debugging</H2
1189 > These options are mainly useful when tracing a problem.
1190 Note that you might also want to invoke
1198 command line option when debugging.
1205 NAME="DEBUG">7.3.1. debug</H4
1209 CLASS="VARIABLELIST"
1215 > Key values that determine what information gets logged to the
1217 HREF="config.html#LOGFILE"
1238 >12289 (i.e.: URLs plus informational and warning messages)</P
1241 >Effect if unset:</DT
1244 > Nothing gets logged.
1251 > The available debug levels are:
1261 CLASS="PROGRAMLISTING"
1262 > debug 1 # show each GET/POST/CONNECT request
1263 debug 2 # show each connection status
1264 debug 4 # show I/O status
1265 debug 8 # show header parsing
1266 debug 16 # log all data into the logfile
1267 debug 32 # debug force feature
1268 debug 64 # debug regular expression filter
1269 debug 128 # debug fast redirects
1270 debug 256 # debug GIF de-animation
1271 debug 512 # Common Log Format
1272 debug 1024 # debug kill pop-ups
1273 debug 4096 # Startup banner and warnings.
1274 debug 8192 # Non-fatal errors</PRE
1281 > To select multiple debug levels, you can either add them or use
1288 > A debug level of 1 is informative because it will show you each request
1289 as it happens. <SPAN
1293 >1, 4096 and 8192 are highly recommended</I
1296 so that you will notice when things go wrong. The other levels are probably
1297 only of interest if you are hunting down a specific problem. They can produce
1298 a hell of an output (especially 16).
1302 > The reporting of <SPAN
1308 > errors (i.e. ones which crash
1312 >) is always on and cannot be disabled.
1315 > If you want to use CLF (Common Log Format), you should set <SPAN
1325 > and not enable anything else.
1336 NAME="SINGLE-THREADED">7.3.2. single-threaded</H4
1340 CLASS="VARIABLELIST"
1346 > Whether to run only one server thread
1374 >Effect if unset:</DT
1377 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1378 serve multiple requests simultaneously.
1385 > This option is only there for debug purposes and you should never
1386 need to use it. <SPAN
1390 >It will drastically reduce performance.</I
1404 NAME="ACCESS-CONTROL">7.4. Access Control and Security</H2
1406 > This section of the config file controls the security-relevant aspects
1417 NAME="LISTEN-ADDRESS">7.4.1. listen-address</H4
1421 CLASS="VARIABLELIST"
1427 > The IP address and TCP port on which <SPAN
1431 listen for client requests.
1457 >Effect if unset:</DT
1460 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1461 home users who run <SPAN
1464 > on the same machine as
1472 > You will need to configure your browser(s) to this proxy address and port.
1475 > If you already have another service running on port 8118, or if you want to
1476 serve requests from other machines (e.g. on your local network) as well, you
1477 will need to override the default.
1480 > If you leave out the IP address, <SPAN
1484 bind to all interfaces (addresses) on your machine and may become reachable
1485 from the Internet. In that case, consider using <A
1486 HREF="config.html#ACLS"
1487 >access control lists</A
1488 > (ACL's, see below), and/or
1495 > to untrusted users, you will
1496 also want to turn off the <TT
1499 HREF="config.html#ENABLE-EDIT-ACTIONS"
1500 >enable-edit-actions</A
1506 HREF="config.html#ENABLE-REMOTE-TOGGLE"
1507 >enable-remote-toggle</A
1517 > Suppose you are running <SPAN
1521 a machine which has the address 192.168.0.1 on your local private network
1522 (192.168.0.0) and has another outside connection with a different address.
1523 You want it to serve requests from inside only:
1533 CLASS="PROGRAMLISTING"
1534 > listen-address 192.168.0.1:8118</PRE
1549 NAME="TOGGLE">7.4.2. toggle</H4
1553 CLASS="VARIABLELIST"
1559 > Initial state of "toggle" status
1575 >Effect if unset:</DT
1578 > Act as if toggled on
1585 > If set to 0, <SPAN
1591 >"toggled off"</SPAN
1592 > mode, i.e. behave like a normal, content-neutral
1593 proxy where all ad blocking, filtering, etc are disabled. See
1596 >enable-remote-toggle</TT
1597 > below. This is not really useful
1598 anymore, since toggling is much easier via <A
1599 HREF="http://config.privoxy.org/toggle"
1601 >the web interface</A
1609 > The windows version will only display the toggle icon in the system tray
1610 if this option is present.
1621 NAME="ENABLE-REMOTE-TOGGLE">7.4.3. enable-remote-toggle</H4
1625 CLASS="VARIABLELIST"
1631 > Whether or not the <A
1632 HREF="http://config.privoxy.org/toggle"
1652 >Effect if unset:</DT
1655 > The web-based toggle feature is disabled.
1662 > When toggled off, <SPAN
1665 > acts like a normal,
1666 content-neutral proxy, i.e. it acts as if none of the actions applied to
1670 > For the time being, access to the toggle feature can <SPAN
1677 controlled separately by <SPAN
1680 > or HTTP authentication,
1681 so that everybody who can access <SPAN
1692 toggle it for all users. So this option is <SPAN
1699 for multi-user environments with untrusted users.
1702 > Note that you must have compiled <SPAN
1706 support for this feature, otherwise this option has no effect.
1717 NAME="ENABLE-EDIT-ACTIONS">7.4.4. enable-edit-actions</H4
1721 CLASS="VARIABLELIST"
1727 > Whether or not the <A
1728 HREF="http://config.privoxy.org/show-status"
1748 >Effect if unset:</DT
1751 > The web-based actions file editor is disabled.
1758 > For the time being, access to the editor can <SPAN
1765 controlled separately by <SPAN
1768 > or HTTP authentication,
1769 so that everybody who can access <SPAN
1780 modify its configuration for all users. So this option is <SPAN
1787 > for multi-user environments with untrusted users.
1790 > Note that you must have compiled <SPAN
1794 support for this feature, otherwise this option has no effect.
1805 NAME="ACLS">7.4.5. ACLs: permit-access and deny-access</H4
1807 NAME="PERMIT-ACCESS"
1815 CLASS="VARIABLELIST"
1821 > Who can access what.
1863 > are IP addresses in dotted decimal notation or valid
1875 > are subnet masks in CIDR notation, i.e. integer
1876 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1877 destination part are optional.
1893 >Effect if unset:</DT
1896 > Don't restrict access further than implied by <TT
1906 > Access controls are included at the request of ISPs and systems
1907 administrators, and <SPAN
1911 >are not usually needed by individual users</I
1914 For a typical home user, it will normally suffice to ensure that
1918 > only listens on the localhost
1919 (127.0.0.1) or internal (home) network address by means of the
1921 HREF="config.html#LISTEN-ADDRESS"
1933 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
1934 for a firewall or to encourage anyone to defer addressing basic security
1938 > Multiple ACL lines are OK.
1939 If any ACLs are specified, then the <SPAN
1943 talks only to IP addresses that match at least one <TT
1947 and don't match any subsequent <TT
1950 > line. In other words, the
1951 last match wins, with the default being <TT
1960 > is using a forwarder (see <TT
1964 for a particular destination URL, the <TT
1970 that is examined is the address of the forwarder and <SPAN
1977 of the ultimate target. This is necessary because it may be impossible for the local
1981 > to determine the IP address of the
1982 ultimate target (that's often what gateways are used for).
1985 > You should prefer using IP addresses over DNS names, because the address lookups take
1986 time. All DNS names must resolve! You can <SPAN
1992 > use domain patterns
1996 > or partial domain names. If a DNS name resolves to multiple
1997 IP addresses, only the first one is used.
2000 > Denying access to particular sites by ACL may have undesired side effects
2001 if the site in question is hosted on a machine which also hosts other sites.
2008 > Explicitly define the default behavior if no ACL and
2016 is OK. The absence of a <TT
2028 > destination addresses are OK:
2039 > permit-access localhost</PRE
2046 > Allow any host on the same class C subnet as www.privoxy.org access to
2047 nothing but www.example.com:
2058 > permit-access www.privoxy.org/24 www.example.com/32</PRE
2065 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
2066 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
2077 > permit-access 192.168.45.64/26
2078 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2093 NAME="BUFFER-LIMIT">7.4.6. buffer-limit</H4
2097 CLASS="VARIABLELIST"
2103 > Maximum size of the buffer for content filtering.
2119 >Effect if unset:</DT
2122 > Use a 4MB (4096 KB) limit.
2129 > For content filtering, i.e. the <TT
2136 > actions, it is necessary that
2140 > buffers the entire document body.
2141 This can be potentially dangerous, since a server could just keep sending
2142 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2146 > When a document buffer size reaches the <TT
2150 flushed to the client unfiltered and no further attempt to
2151 filter the rest of the document is made. Remember that there may be multiple threads
2152 running, which might require up to <TT
2162 >, unless you have enabled <SPAN
2164 >"single-threaded"</SPAN
2178 NAME="FORWARDING">7.5. Forwarding</H2
2180 > This feature allows routing of HTTP requests through a chain of
2182 It can be used to better protect privacy and confidentiality when
2183 accessing specific domains by routing requests to those domains
2184 through an anonymous public proxy (see e.g. <A
2185 HREF="http://www.multiproxy.org/anon_list.htm"
2187 >http://www.multiproxy.org/anon_list.htm</A
2189 Or to use a caching proxy to speed up browsing. Or chaining to a parent
2190 proxy may be necessary because the machine that <SPAN
2194 runs on has no direct Internet access.</P
2196 > Also specified here are SOCKS proxies. <SPAN
2200 supports the SOCKS 4 and SOCKS 4A protocols.</P
2206 NAME="FORWARD">7.5.1. forward</H4
2210 CLASS="VARIABLELIST"
2216 > To which parent HTTP proxy specific requests should be routed.
2252 > is a domain name pattern (see the
2253 chapter on domain matching in the <TT
2262 > is the address of the parent HTTP proxy
2263 as an IP addresses in dotted decimal notation or as a valid DNS name (or <SPAN
2269 >"no forwarding"</SPAN
2276 > parameters are TCP ports, i.e. integer
2277 values from 1 to 64535
2293 >Effect if unset:</DT
2296 > Don't use parent HTTP proxies.
2311 >, then requests are not
2312 forwarded to another HTTP proxy but are made directly to the web servers.
2315 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2322 > Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
2333 > forward .* anon-proxy.example.org:8080
2341 > Everything goes to our example ISP's caching proxy, except for requests
2342 to that ISP's sites:
2353 > forward .*. caching-proxy.example-isp.net:8000
2354 forward .example-isp.net .</PRE
2369 NAME="SOCKS">7.5.2. forward-socks4 and forward-socks4a</H4
2371 NAME="FORWARD-SOCKS4"
2374 NAME="FORWARD-SOCKS4A"
2379 CLASS="VARIABLELIST"
2385 > Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
2432 > is a domain name pattern (see the
2433 chapter on domain matching in the <TT
2448 are IP addresses in dotted decimal notation or valid DNS names (<TT
2459 >"no HTTP forwarding"</SPAN
2460 >), and the optional
2466 > parameters are TCP ports, i.e. integer values from 1 to 64535
2482 >Effect if unset:</DT
2485 > Don't use SOCKS proxies.
2492 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2495 > The difference between <TT
2500 >forward-socks4a</TT
2502 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2503 server, while in SOCKS 4 it happens locally.
2514 >, then requests are not
2515 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2523 > From the company example.com, direct connections are made to all
2527 > domains, but everything outbound goes through
2528 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2540 > forward-socks4a .*. socks-gw.example.com:1080 www-cache.example-isp.net:8080
2541 forward .example.com .</PRE
2548 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2559 > forward-socks4 .*. socks-gw.example.com:1080 .</PRE
2574 NAME="ADVANCED-FORWARDING-EXAMPLES">7.5.3. Advanced Forwarding Examples</H4
2576 > If you have links to multiple ISPs that provide various special content
2577 only to their subscribers, you can configure multiple <SPAN
2581 which have connections to the respective ISPs to act as forwarders to each other, so that
2588 > users can see the internal content of all ISPs.</P
2590 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2591 isp-b.net. Both run <SPAN
2595 configuration can look like this:</P
2608 forward .isp-b.net host-b:8118</PRE
2625 forward .isp-a.net host-a:8118</PRE
2631 > Now, your users can set their browser's proxy to use either
2632 host-a or host-b and be able to browse the internal content
2633 of both isp-a and isp-b.</P
2635 > If you intend to chain <SPAN
2642 > locally, then chain as
2645 >browser -> squid -> privoxy</TT
2646 > is the recommended way. </P
2648 > Assuming that <SPAN
2655 run on the same box, your <SPAN
2658 > configuration could then look like this:</P
2668 > # Define Privoxy as parent proxy (without ICP)
2669 cache_peer 127.0.0.1 parent 8118 7 no-query
2671 # Define ACL for protocol FTP
2674 # Do not forward FTP requests to Privoxy
2675 always_direct allow ftp
2677 # Forward all the rest to Privoxy
2678 never_direct allow all</PRE
2684 > You would then need to change your browser's proxy settings to <SPAN
2687 >'s address and port.
2688 Squid normally uses port 3128. If unsure consult <TT
2702 NAME="WINDOWS-GUI">7.6. Windows GUI Options</H2
2707 > has a number of options specific to the
2708 Windows GUI interface:</P
2710 NAME="ACTIVITY-ANIMATION"
2715 >"activity-animation"</SPAN
2720 > icon will animate when
2724 > is active. To turn off, set to 0.</P
2729 CLASS="LITERALLAYOUT"
2734 >activity-animation 1</I
2737 </P
2747 >"log-messages"</SPAN
2752 > will log messages to the console
2758 CLASS="LITERALLAYOUT"
2766 </P
2771 NAME="LOG-BUFFER-SIZE"
2777 >"log-buffer-size"</SPAN
2778 > is set to 1, the size of the log buffer,
2779 i.e. the amount of memory used for the log messages displayed in the
2780 console window, will be limited to <SPAN
2782 >"log-max-lines"</SPAN
2785 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
2786 eat up all your memory!</P
2791 CLASS="LITERALLAYOUT"
2796 >log-buffer-size 1</I
2799 </P
2804 NAME="LOG-MAX-LINES"
2809 >log-max-lines</SPAN
2810 > is the maximum number of lines held
2811 in the log buffer. See above.</P
2816 CLASS="LITERALLAYOUT"
2821 >log-max-lines 200</I
2824 </P
2829 NAME="LOG-HIGHLIGHT-MESSAGES"
2834 >"log-highlight-messages"</SPAN
2839 > will highlight portions of the log
2840 messages with a bold-faced font:</P
2845 CLASS="LITERALLAYOUT"
2850 >log-highlight-messages 1</I
2853 </P
2858 NAME="LOG-FONT-NAME"
2861 > The font used in the console window:</P
2866 CLASS="LITERALLAYOUT"
2871 >log-font-name Comic Sans MS</I
2874 </P
2879 NAME="LOG-FONT-SIZE"
2882 > Font size used in the console window:</P
2887 CLASS="LITERALLAYOUT"
2895 </P
2900 NAME="SHOW-ON-TASK-BAR"
2906 >"show-on-task-bar"</SPAN
2907 > controls whether or not
2911 > will appear as a button on the Task bar
2917 CLASS="LITERALLAYOUT"
2922 >show-on-task-bar 0</I
2925 </P
2930 NAME="CLOSE-BUTTON-MINIMIZES"
2935 >"close-button-minimizes"</SPAN
2936 > is set to 1, the Windows close
2937 button will minimize <SPAN
2940 > instead of closing
2941 the program (close with the exit option on the File menu).</P
2946 CLASS="LITERALLAYOUT"
2951 >close-button-minimizes 1</I
2954 </P
2964 >"hide-console"</SPAN
2965 > option is specific to the MS-Win console
2969 >. If this option is used,
2973 > will disconnect from and hide the
2979 CLASS="LITERALLAYOUT"
2987 </P
2998 SUMMARY="Footer navigation table"
3009 HREF="configuration.html"
3027 HREF="actions-file.html"