Sponsored Content
Full Discussion: Unix log treatment
Top Forums Shell Programming and Scripting Unix log treatment Post 48298 by farzolito on Wednesday 3rd of March 2004 04:41:14 AM
Old 03-03-2004
thank you very much for your answer Smilie
my problem is resolved.

Smilie
 

9 More Discussions You Might Find Interesting

1. Cybersecurity

UNIX error log

system administration utility has recently been installed at the SCO Openserver (UNIX) servers of our bank. While receiving the error log files of this utility, we have noted the following warning messages: <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> · ... (0 Replies)
Discussion started by: eysheikah
0 Replies

2. Cybersecurity

UNIX error log

A system administration utility has recently been installed at the SCO Openserver (UNIX) servers of our bank. While receiving the error log files of this utility, we have noted the following warning messages: <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> · ... (3 Replies)
Discussion started by: eysheikah
3 Replies

3. UNIX for Dummies Questions & Answers

Cannot Log-in Unix Server

I an receiving an error message when logging in as root the message is "out of inodes on EAFS dev hd 1/40 -- I cannot get in at all can someone help - we are shut down (2 Replies)
Discussion started by: Bev
2 Replies

4. Shell Programming and Scripting

Log of the Unix script

Hi, I have written a Unix shell script that does different things like copying the files from location to another etc depending on various conditions. There are print statements in the script. The problem is I want the script to log the activity in a file right from the moment the script... (1 Reply)
Discussion started by: srinik20
1 Replies

5. Shell Programming and Scripting

alert_oss.log oracle log file in hp-unix

Hi I have go this alert_oss.log that is basically capturing all the oracle errorlogs.Now the problem is that it is one huge file and to see log of some particular date i tried cat alert_oss.log | grep 'Mar 25 10:44:45 2007' > alert_25.txt is not giving me the required output. pls suggest ... (3 Replies)
Discussion started by: Assassin
3 Replies

6. UNIX for Advanced & Expert Users

unix log file

Hi I want to know where the unix log file is stored I couldnt fınd anythıng under var/log directory Regards (8 Replies)
Discussion started by: tjay83
8 Replies

7. Shell Programming and Scripting

Error in multiple files treatment with AWK

Hello, My code is like that: awk -v f=92238 '$1~/^m2/{tok1=1;next}tok1==1&&$0~f{tok1=0;print $NF}' inp. inp.1 Eahc of the "inp.*" file is like that: ... m1 xxxx xxxx 92238 897987 xxxx xxxx m2 xxxx xxxx 92238 123435 xxxx xxxx ... (1 Reply)
Discussion started by: jolecanard
1 Replies

8. UNIX for Dummies Questions & Answers

unix log files

The unix admins in work have forced us to use a custom restricted shell on one of our servers.From what i can tell, this shell tags log messages (using /usr/bin/logger) with various info (date, hostname, user, connection info, etc...). It also forces the execution of commands through ksh.I've not... (2 Replies)
Discussion started by: Irrational
2 Replies

9. Shell Programming and Scripting

Unix Log out time

Hi, Is there a way to find out the logout date for a user who has been logged in to the system for more than 1 day. For example, the below user as indicated by the "last" command had logged into the system on Mar 8 and he has been online for 2 days and 6:53 hour:min. So basically, he logged out... (2 Replies)
Discussion started by: devtakh
2 Replies
VARNISHLOG(1)															     VARNISHLOG(1)

NAME
varnishlog - Display Varnish logs SYNOPSIS
varnishlog [-a] [-b] [-C] [-c] [-D] [-d] [-I regex] [-i tag] [-k keep] [-n varnish_name] [-o] [-O] [-m tag:regex ...] [-P file] [-r file] [-s num] [-u] [-V] [-w file] [-X regex] [-x tag] DESCRIPTION
The varnishlog 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, varnishlog 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, varnishlog acts as if they both were. -D Daemonize. -d Process old log entries on startup. Normally, varnishlog 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. -m tag:regex only list transactions where tag matches regex. Multiple -m options are AND-ed together. Can not be combined with -O -n Specifies the name of the varnishd instance to get logs from. If -n is not specified, the host name is used. -o Ignored for compatibility with earlier versions. -O Do not group log entries by request ID. Can not be combined with -m. -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 var- nishlog 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. TAGS
The following log entry tags are currently defined: o Backend o BackendClose o BackendOpen o BackendReuse o BackendXID o CLI o ClientAddr o Debug o Error o ExpBan o ExpKill o ExpPick o Hit o HitPass o HttpError o HttpGarbage o Length o ObjHeader o ObjLostHeader o ObjProtocol o ObjRequest o ObjResponse o ObjStatus o ObjURL o ReqEnd o ReqStart o RxHeader o RxLostHeader o RxProtocol o RxRequest o RxResponse o RxStatus o RxURL o SessionClose o SessionOpen o StatAddr o StatSess o TTL o TxHeader o TxLostHeader o TxProtocol o TxRequest o TxResponse o TxStatus o TxURL o VCL_acl o VCL_call o VCL_return o VCL_trace o 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 -m 'RxURL:^/$' SEE ALSO
o varnishd(1) o varnishhist(1) o varnishncsa(1) o varnishstat(1) o varnishtop(1) HISTORY
The varnishlog utility was developed by Poul-Henning Kamp <phk@phk.freebsd.dk> in cooperation with Verdens Gang AS, Varnish Software AS and Varnish Software. This manual page was initially written by Dag-Erling Smorgrav. COPYRIGHT
This document is licensed under the same licence as Varnish itself. See LICENCE for details. o Copyright (c) 2006 Verdens Gang AS o Copyright (c) 2006-2011 Varnish Software AS AUTHOR
Dag-Erling Smorgrav, Per Buer 0.2 2010-05-31 VARNISHLOG(1)
All times are GMT -4. The time now is 08:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy