Linux server.kiran-academy.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
: 194.233.91.196 | : 216.73.216.172
Cant Read [ /etc/named.conf ]
7.4.32
finalho
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
varnish-5.2.1 /
html /
users-guide /
[ HOME SHELL ]
Name
Size
Permission
Action
command-line.html
10.23
KB
-rw-r--r--
compression.html
11.79
KB
-rw-r--r--
devicedetection.html
21.88
KB
-rw-r--r--
esi.html
11.71
KB
-rw-r--r--
increasing-your-hitrate.html
61.46
KB
-rw-r--r--
index.html
11.92
KB
-rw-r--r--
intro.html
10.24
KB
-rw-r--r--
operation-logging.html
9.3
KB
-rw-r--r--
operation-statistics.html
8.39
KB
-rw-r--r--
params.html
5.66
KB
-rw-r--r--
performance.html
10.05
KB
-rw-r--r--
purging.html
13.81
KB
-rw-r--r--
report.html
5.48
KB
-rw-r--r--
run_cli.html
15.13
KB
-rw-r--r--
run_security.html
17.29
KB
-rw-r--r--
running.html
7.21
KB
-rw-r--r--
sizing-your-cache.html
6.17
KB
-rw-r--r--
storage-backends.html
11.52
KB
-rw-r--r--
troubleshooting.html
16.57
KB
-rw-r--r--
vcl-actions.html
6.04
KB
-rw-r--r--
vcl-backends.html
21.2
KB
-rw-r--r--
vcl-built-in-subs.html
31.33
KB
-rw-r--r--
vcl-example-acls.html
5.87
KB
-rw-r--r--
vcl-example-manipulating-heade...
6.33
KB
-rw-r--r--
vcl-example-manipulating-respo...
6.47
KB
-rw-r--r--
vcl-example-websockets.html
6.95
KB
-rw-r--r--
vcl-examples.html
5.68
KB
-rw-r--r--
vcl-grace.html
9.83
KB
-rw-r--r--
vcl-hashing.html
8.52
KB
-rw-r--r--
vcl-inline-c.html
6.14
KB
-rw-r--r--
vcl-separate.html
13.18
KB
-rw-r--r--
vcl-syntax.html
10.49
KB
-rw-r--r--
vcl-variables.html
5.93
KB
-rw-r--r--
vcl.html
7.72
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : run_cli.html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <title>CLI - bossing Varnish around — Varnish version 5.2.1 documentation</title> <link rel="stylesheet" href="../_static/classic.css" type="text/css" /> <link rel="stylesheet" href="../_static/pygments.css" type="text/css" /> <script type="text/javascript"> var DOCUMENTATION_OPTIONS = { URL_ROOT: '../', VERSION: '5.2.1', COLLAPSE_INDEX: false, FILE_SUFFIX: '.html', HAS_SOURCE: true }; </script> <script type="text/javascript" src="../_static/jquery.js"></script> <script type="text/javascript" src="../_static/underscore.js"></script> <script type="text/javascript" src="../_static/doctools.js"></script> <link rel="index" title="Index" href="../genindex.html" /> <link rel="search" title="Search" href="../search.html" /> <link rel="top" title="Varnish version 5.2.1 documentation" href="../index.html" /> <link rel="up" title="Starting and running Varnish" href="running.html" /> <link rel="next" title="Storage backends" href="storage-backends.html" /> <link rel="prev" title="Important command line arguments" href="command-line.html" /> </head> <body role="document"> <div class="related" role="navigation" aria-label="related navigation"> <h3>Navigation</h3> <ul> <li class="right" style="margin-right: 10px"> <a href="../genindex.html" title="General Index" accesskey="I">index</a></li> <li class="right" > <a href="storage-backends.html" title="Storage backends" accesskey="N">next</a> |</li> <li class="right" > <a href="command-line.html" title="Important command line arguments" accesskey="P">previous</a> |</li> <li class="nav-item nav-item-0"><a href="../index.html">Varnish version 5.2.1 documentation</a> »</li> <li class="nav-item nav-item-1"><a href="index.html" >The Varnish Users Guide</a> »</li> <li class="nav-item nav-item-2"><a href="running.html" accesskey="U">Starting and running Varnish</a> »</li> </ul> </div> <div class="document"> <div class="documentwrapper"> <div class="bodywrapper"> <div class="body" role="main"> <div class="section" id="cli-bossing-varnish-around"> <span id="run-cli"></span><h1>CLI - bossing Varnish around<a class="headerlink" href="#cli-bossing-varnish-around" title="Permalink to this headline">¶</a></h1> <p>Once <cite>varnishd</cite> is started, you can control it using the command line interface.</p> <p>The easiest way to do this, is using <cite>varnishadm</cite> on the same machine as <cite>varnishd</cite> is running:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnishadm</span> <span class="n">help</span> </pre></div> </div> <p>If you want to run <cite>varnishadm</cite> from a remote system, you can do it two ways.</p> <p>You can SSH into the <cite>varnishd</cite> computer and run <cite>varnishadm</cite>:</p> <div class="highlight-default"><div class="highlight"><pre><span></span>ssh $http_front_end varnishadm help </pre></div> </div> <p>But you can also configure <cite>varnishd</cite> to accept remote CLI connections (using the '-T' and '-S' arguments):</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnishd</span> <span class="o">-</span><span class="n">T</span> <span class="p">:</span><span class="mi">6082</span> <span class="o">-</span><span class="n">S</span> <span class="o">/</span><span class="n">etc</span><span class="o">/</span><span class="n">varnish_secret</span> </pre></div> </div> <p>And then on the remote system run <cite>varnishadm</cite>:</p> <div class="highlight-default"><div class="highlight"><pre><span></span>varnishadm -T $http_front_end -S /etc/copy_of_varnish_secret help </pre></div> </div> <p>but as you can see, SSH is much more convenient.</p> <p>If you run <cite>varnishadm</cite> without arguments, it will read CLI commands from <cite>stdin</cite>, if you give it arguments, it will treat those as the single CLI command to execute.</p> <p>The CLI always returns a status code to tell how it went: '200' means OK, anything else means there were some kind of trouble.</p> <p><cite>varnishadm</cite> will exit with status 1 and print the status code on standard error if it is not 200.</p> <div class="section" id="what-can-you-do-with-the-cli"> <h2>What can you do with the CLI<a class="headerlink" href="#what-can-you-do-with-the-cli" title="Permalink to this headline">¶</a></h2> <p>The CLI gives you almost total control over <cite>varnishd</cite> some of the more important tasks you can perform are:</p> <ul class="simple"> <li>load/use/discard VCL programs</li> <li>ban (invalidate) cache content</li> <li>change parameters</li> <li>start/stop worker process</li> </ul> <p>We will discuss each of these briefly below.</p> <div class="section" id="load-use-and-discard-vcl-programs"> <h3>Load, use and discard VCL programs<a class="headerlink" href="#load-use-and-discard-vcl-programs" title="Permalink to this headline">¶</a></h3> <p>All caching and policy decisions are made by VCL programs.</p> <p>You can have multiple VCL programs loaded, but one of them is designated the "active" VCL program, and this is where all new requests start out.</p> <p>To load new VCL program:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">vcl</span><span class="o">.</span><span class="n">load</span> <span class="n">some_name</span> <span class="n">some_filename</span> </pre></div> </div> <p>Loading will read the VCL program from the file, and compile it. If the compilation fails, you will get an error messages:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="o">.../</span><span class="n">mask</span> <span class="ow">is</span> <span class="ow">not</span> <span class="n">numeric</span><span class="o">.</span> <span class="p">(</span><span class="s1">'input'</span> <span class="n">Line</span> <span class="mi">4</span> <span class="n">Pos</span> <span class="mi">17</span><span class="p">)</span> <span class="s2">"192.168.2.0/24x"</span><span class="p">,</span> <span class="o">----------------</span><span class="c1">#################-</span> <span class="n">Running</span> <span class="n">VCC</span><span class="o">-</span><span class="n">compiler</span> <span class="n">failed</span><span class="p">,</span> <span class="n">exit</span> <span class="mi">1</span> <span class="n">VCL</span> <span class="n">compilation</span> <span class="n">failed</span> </pre></div> </div> <p>If compilation succeeds, the VCL program is loaded, and you can now make it the active VCL, whenever you feel like it:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">vcl</span><span class="o">.</span><span class="n">use</span> <span class="n">some_name</span> </pre></div> </div> <p>If you find out that was a really bad idea, you can switch back to the previous VCL program again:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">vcl</span><span class="o">.</span><span class="n">use</span> <span class="n">old_name</span> </pre></div> </div> <p>The switch is instantaneous, all new requests will start using the VCL you activated right away. The requests currently being processed complete using whatever VCL they started with.</p> <p>It is good idea to design an emergency-VCL before you need it, and always have it loaded, so you can switch to it with a single vcl.use command.</p> </div> <div class="section" id="ban-cache-content"> <h3>Ban cache content<a class="headerlink" href="#ban-cache-content" title="Permalink to this headline">¶</a></h3> <p>Varnish offers "purges" to remove things from cache, provided that you know exactly what they are.</p> <p>But sometimes it is useful to be able to throw things out of cache without having an exact list of what to throw out.</p> <p>Imagine for instance that the company logo changed and now you need Varnish to stop serving the old logo out of the cache:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">ban</span> <span class="n">req</span><span class="o">.</span><span class="n">url</span> <span class="o">~</span> <span class="s2">"logo.*[.]png"</span> </pre></div> </div> <p>should do that, and yes, that is a regular expression.</p> <p>We call this "banning" because the objects are still in the cache, but they are banned from delivery.</p> <p>Instead of checking each and every cached object right away, we test each object against the regular expression only if and when an HTTP request asks for it.</p> <p>Banning stuff is much cheaper than restarting Varnish to get rid of wronly cached content.</p> </div> <div class="section" id="change-parameters"> <h3>Change parameters<a class="headerlink" href="#change-parameters" title="Permalink to this headline">¶</a></h3> <p>Parameters can be set on the command line with the '-p' argument, but they can also be examined and changed on the fly from the CLI:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">param</span><span class="o">.</span><span class="n">show</span> <span class="n">prefer_ipv6</span> <span class="mi">200</span> <span class="n">prefer_ipv6</span> <span class="n">off</span> <span class="p">[</span><span class="nb">bool</span><span class="p">]</span> <span class="n">Default</span> <span class="ow">is</span> <span class="n">off</span> <span class="n">Prefer</span> <span class="n">IPv6</span> <span class="n">address</span> <span class="n">when</span> <span class="n">connecting</span> <span class="n">to</span> <span class="n">backends</span> <span class="n">which</span> <span class="n">have</span> <span class="n">both</span> <span class="n">IPv4</span> <span class="ow">and</span> <span class="n">IPv6</span> <span class="n">addresses</span><span class="o">.</span> <span class="n">varnish</span><span class="o">></span> <span class="n">param</span><span class="o">.</span><span class="n">set</span> <span class="n">prefer_ipv6</span> <span class="n">true</span> <span class="mi">200</span> </pre></div> </div> <p>In general it is not a good idea to modify parameters unless you have a good reason, such as performance tuning or security configuration.</p> <p>Most parameters will take effect instantly, or with a natural delay of some duration,</p> <p>but a few of them requires you to restart the child process before they take effect. This is always noted in the description of the parameter.</p> </div> <div class="section" id="starting-and-stopping-the-worker-process"> <h3>Starting and stopping the worker process<a class="headerlink" href="#starting-and-stopping-the-worker-process" title="Permalink to this headline">¶</a></h3> <p>In general you should just leave the worker process running, but if you need to stop and/or start it, the obvious commands work:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">stop</span> </pre></div> </div> <p>and:</p> <div class="highlight-default"><div class="highlight"><pre><span></span><span class="n">varnish</span><span class="o">></span> <span class="n">start</span> </pre></div> </div> <p>If you start <cite>varnishd</cite> with the '-d' (debugging) argument, you will always need to start the child process explicitly.</p> <p>Should the child process die, the master process will automatically restart it, but you can disable that with the 'auto_restart' parameter.</p> </div> </div> </div> </div> </div> </div> <div class="sphinxsidebar" role="navigation" aria-label="main navigation"> <div class="sphinxsidebarwrapper"> <h3><a href="../index.html">Table Of Contents</a></h3> <ul> <li><a class="reference internal" href="#">CLI - bossing Varnish around</a><ul> <li><a class="reference internal" href="#what-can-you-do-with-the-cli">What can you do with the CLI</a><ul> <li><a class="reference internal" href="#load-use-and-discard-vcl-programs">Load, use and discard VCL programs</a></li> <li><a class="reference internal" href="#ban-cache-content">Ban cache content</a></li> <li><a class="reference internal" href="#change-parameters">Change parameters</a></li> <li><a class="reference internal" href="#starting-and-stopping-the-worker-process">Starting and stopping the worker process</a></li> </ul> </li> </ul> </li> </ul> <h4>Previous topic</h4> <p class="topless"><a href="command-line.html" title="previous chapter">Important command line arguments</a></p> <h4>Next topic</h4> <p class="topless"><a href="storage-backends.html" title="next chapter">Storage backends</a></p> <div role="note" aria-label="source link"> <h3>This Page</h3> <ul class="this-page-menu"> <li><a href="../_sources/users-guide/run_cli.txt" rel="nofollow">Show Source</a></li> </ul> </div> <div id="searchbox" style="display: none" role="search"> <h3>Quick search</h3> <form class="search" action="../search.html" method="get"> <div><input type="text" name="q" /></div> <div><input type="submit" value="Go" /></div> <input type="hidden" name="check_keywords" value="yes" /> <input type="hidden" name="area" value="default" /> </form> </div> <script type="text/javascript">$('#searchbox').show(0);</script> </div> </div> <div class="clearer"></div> </div> <div class="related" role="navigation" aria-label="related navigation"> <h3>Navigation</h3> <ul> <li class="right" style="margin-right: 10px"> <a href="../genindex.html" title="General Index" >index</a></li> <li class="right" > <a href="storage-backends.html" title="Storage backends" >next</a> |</li> <li class="right" > <a href="command-line.html" title="Important command line arguments" >previous</a> |</li> <li class="nav-item nav-item-0"><a href="../index.html">Varnish version 5.2.1 documentation</a> »</li> <li class="nav-item nav-item-1"><a href="index.html" >The Varnish Users Guide</a> »</li> <li class="nav-item nav-item-2"><a href="running.html" >Starting and running Varnish</a> »</li> </ul> </div> <div class="footer" role="contentinfo"> © Copyright 2010-2014, Varnish Software AS. Created using <a href="http://sphinx-doc.org/">Sphinx</a> 1.4.9. </div> </body> </html>
Close