Rechercher une page de manuel

Chercher une autre page de manuel:

varnishlog

Langue: en

Autres versions - même langue

Version: 371687 (fedora - 01/12/10)

Section: 1 (Commandes utilisateur)


BSD mandoc

NAME

varnishlog - Display Varnish logs

SYNOPSIS

[-a ] [-b ] [-C ] [-c ] [-D ] [-d ] [-I regex ] [-i tag ] [-k keep ] [-n varnish_name ] [-o ] [-P file ] [-r file ] [-s num ] [-u ] [-V ] [-w file ] [-X regex ] [-x tag ] [tag regex ]

DESCRIPTION

The utility reads and presents varnishd(1) shared memory logs.

The following options are available:

-a
When writing to a file, append to it rather than overwrite it.
-b
Include log entries which result from communication with a backend server. If neither -b nor -c is specified, acts as if they both were.
-C
Ignore case when matching regular expressions.
-c
Include log entries which result from communication with a client. If neither -b nor -c is specified, acts as if they both were.
-D
Daemonize.
-d
Process old log entries on startup. Normally, will only process entries which are written to the log after it starts.
-I regex
Include log entries which match the specified regular expression. If neither -I nor -i is specified, all log entries are included.
-i tag
Include log entries with the specified tag. If neither -I nor -i is specified, all log entries are included.
-k num
Only show the first num log records.
-n
Specifies the name of the varnishd instance to get logs from. If -n is not specified, the host name is used.
-o
Group log entries by request ID. This has no effect when writing to a file using the -w option.
-P file
Write the process's PID to the specified file
-r file
Read log entries from file instead of shared memory.
-s num
Skip the first num log records.
-u
Unbuffered output.
-V
Display the version number and exit.
-w file
Write log entries to file instead of displaying them. The file will be overwritten unless the -a option was specified.

If receives a SIGHUP while writing to a file, it will reopen the file, allowing the old one to be rotated away.

-X regex
Exclude log entries which match the specified regular expression.
-x tag
Exclude log entries with the specified tag.

If the -o option was specified, an additional tag and regex may be specified to select only requests which generated a log entry with the given tag whose contents match the given regex

TAGS

The following log entry tags are currently defined:
Backend
BackendClose
BackendOpen
BackendReuse
BackendXID
CLI
ClientAddr
Debug
Error
ExpBan
ExpKill
ExpPick
Hit
HitPass
HttpError
HttpGarbage
Length
ObjHeader
ObjLostHeader
ObjProtocol
ObjRequest
ObjResponse
ObjStatus
ObjURL
ReqEnd
ReqStart
RxHeader
RxLostHeader
RxProtocol
RxRequest
RxResponse
RxStatus
RxURL
SessionClose
SessionOpen
StatAddr
StatSess
TTL
TxHeader
TxLostHeader
TxProtocol
TxRequest
TxResponse
TxStatus
TxURL
VCL_acl
VCL_call
VCL_return
VCL_trace
WorkThread

EXAMPLES

The following command line simply copies all log entries to a log file:
 $ varnishlog -w /var/log/varnish.log
 

The following command line reads that same log file and displays requests for the front page:

 $ varnishlog -r /var/log/varnish.log -c -o RxURL '^/$'
 

SEE ALSO

varnishd(1), varnishhist(1), varnishncsa(1), varnishstat(1), varnishtop(1)

HISTORY

The utility was developed by An Poul-Henning Kamp Aq phk@phk.freebsd.dk in cooperation with Verdens Gang AS and Linpro AS. This manual page was written by An Dag-Erling Sm/orgrav Aq des@des.no .
En fait, MultideskOS fonctionne assez rapidement, il est même beaucoup
plus rapide que Windows dans beaucoup de situations, parce que le temps
de chargement ( disque ) d'un programme de 1 Mo est plus lent que celle
d'un programme de 3 à 50 Ko, et que les calculs processeur mettent moins
de temps que les accès disques. C'est pour cette raison notemment que
les PC portables sont plus rapides. Ils ont en effet un disque de
dimention plus petite. De plus, le système n'a plus besoin de SWAP
(Cache disque), à cause des petites tailles. De ce fait, on evite un
fichier de 250 Mo sur le disque ainsi que des vas et viens réguliers de
la tete, que Windows fait pour lire une partie du programme et pour
mettre cette partie dans le fichier SWAP, avant d'y accéder à nouveau
pour la relire comme si c'etait de la mémoire RAM. Les caches disques
sont ridicules de nos jours, avec 256 Mo de RAM, Windows RAM encore,
alors que MultideskOS tourne sans rien dire a partir de 16 Mo, 8 Mo
étant le minimum. Nous avons testé, MultideskOS est aussi rapide sur un
486 - 66 Mhz que Windows sur un Athlon 750 Mhz. Sur ce mme Athlon,
MultideskOS démarre entre 2 et 5 secondes, alors que Windows +- en 30
secondes.
-- Jayce - Vous n'y connaissez rien au matos. --