06-24-2009
Quote:
Originally Posted by
chatwizrd
tail -f log.log | egrep -i 'cat|dog'
Are you sure that is not
or rather than
and? It is showing lines with just one string in.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello again, I'm still working on the redo of my script I created before and came across a grep question.
I'm on SunOS 5.9 and using the Korn Shell. I'm writing a function to check for validation of root disks being mirrored. If the server allows me to use metastat, I'm looking to show it has... (4 Replies)
Discussion started by: Janus
4 Replies
2. Shell Programming and Scripting
suppose i have a file structure(serial file)--
----------
----------
---------
summery
--------
------
--------
finished
-----
-------
i want to fetch lines from summery to finished
i can get line of summery by grep command. but how can i fetch lines untill it reaches finished.probably... (2 Replies)
Discussion started by: arghya_owen
2 Replies
3. Shell Programming and Scripting
Hi
I am writing a script which should read a file and search for certain strings 'approved' or 'removed' and retain only those lines that contain the above strings.
Ex: file name 'test'
test:
approved package
waiting for approval package
disapproved package
removed package
approved... (14 Replies)
Discussion started by: vj8436
14 Replies
4. Shell Programming and Scripting
Hi folks
I am not allowed to install GNU grep on AIX.
Here my code excerpt:
grep_fatal () {
/usr/sfw/bin/gegrep -B4 -A2 "FATAL|QUEUE|SIGHUP"
}
Howto the same on AIX based machine?
from manual GNU grep
‘--after-context=num’
Print num lines of trailing context after... (4 Replies)
Discussion started by: slashdotweenie
4 Replies
5. Shell Programming and Scripting
I have several very large file that are extracts from Oracle tables. These files are formatted in XML type syntax with multiple entries like:
<ROW>
some information
more information
</ROW>
I want to grep for some words, then print all lines between <ROW> AND </ROW>. Can this be done with AWK?... (7 Replies)
Discussion started by: jbruce
7 Replies
6. Shell Programming and Scripting
Hi,
my xml files looks something like this
<Instance Name="New York">
<Description></Description>
<Instance Name="A">
<Description></Description>
<PropertyValue Key="false" Name="Building A" />
</Instance>
<Instance Name="B">
... (4 Replies)
Discussion started by: tententen
4 Replies
7. Shell Programming and Scripting
Hi,
I have one file, say file 1, that has data like below where 19900107 is the date,
19900107 12 144 129 0.7380047
19900108 12 168 129 0.3149017
19900109 12 192 129 3.2766666E-02
... (3 Replies)
Discussion started by: Wynner
3 Replies
8. Shell Programming and Scripting
I have an input file
12.4 1.72849432773174e+01 -7.74784188610632e+01
12.5 9.59432114416327e-01 -7.87018212757537e+01
15.6 5.20139995965960e-01 -5.61612429666624e+01
29.3 3.76696387248366e+00 -7.42896194101892e+01
32.1 1.86899877018077e+01 -7.56508762501408e+01
35 6.98857157014640e+00... (2 Replies)
Discussion started by: chrisjorg
2 Replies
9. Shell Programming and Scripting
Hello,
I want to extract from a file like :
20120530025502914 | REQUEST | whatever
20120530025502968 | RESPONSE | whatever
20120530025502985 | RESPONSE | whatever
20120530025502996 | REQUEST | whatever
20120530025503013 | REQUEST | whatever
20120530025503045 | RESPONSE | whatever
I want... (14 Replies)
Discussion started by: black_fender
14 Replies
10. Shell Programming and Scripting
say we have :
2914 | REQUEST | whatever
2914 | RESPONSE | whatever
2914 | SUCCESS | whatever
2985 | RESPONSE | whatever
2986 | REQUEST | whatever
2990 | REQUEST | whatever
2985 | RESPONSE | whatever
2996 | REQUEST | whatever
2010 | SUCCESS | whatever
2013 | REQUEST | whatever
2013 |... (7 Replies)
Discussion started by: Saumitra Pandey
7 Replies
LEARN ABOUT DEBIAN
systemd-journalctl
SYSTEMD-JOURNALCTL(1) systemd-journalctl SYSTEMD-JOURNALCTL(1)
NAME
systemd-journalctl - Query the systemd journal
SYNOPSIS
systemd-journalctl [OPTIONS...] [MATCH]
DESCRIPTION
systemd-journalctl may be used to query the contents of the systemd(1) journal.
If called without parameter will show the full contents of the journal, starting with the oldest entry collected.
If a match argument is passed the output is filtered accordingly. A match is in the format FIELD=VALUE, e.g. _SYSTEMD_UNIT=httpd.service.
Output is interleaved from all accessible journal files, whether they are rotated or currently being written, and regardless whether they
belong to the system itself or are accessible user journals.
All users are granted access to their private per-user journals. However, by default only root and users who are members of the adm group
get access to the system journal and the journals of other users.
OPTIONS
The following options are understood:
--help, -h
Prints a short help text and exits.
--version
Prints a short version string and exits.
--no-pager
Do not pipe output into a pager.
--all, -a
Show all fields in full, even if they include unprintable characters or are very long.
--follow, -f
Show only most recent journal entries, and continously print new entries as they are appended to the journal.
--lines=, -n
Controls the number of journal lines to show, counting from the most recent ones. Takes a positive integer argument. In follow mode
defaults to 10, otherwise is unset thus not limiting how many lines are shown.
--no-tail
Show all stored output lines, even in follow mode. Undoes the effect of --lines=.
--output=, -o
Controls the formatting of the journal entries that are shown. Takes one of short, short-monotonic, verbose, export, json, cat. short
is the default and generates an output that is mostly identical to the formatting of classic syslog log files, showing one line per
journal entry. short-monotonic is very similar but shows monotonic timestamps instead of wallclock timestamps. verbose shows the full
structered entry items with all fiels. export serializes the journal into a binary (but mostly text-based) stream suitable for backups
and network transfer. json formats entries as JSON data structures. cat generates a very terse output only showing the actual message
of each journal entry with no meta data, not even a timestamp.
--quiet, -q
Suppresses any warning message regarding inaccessable system journals when run as normal user.
--new-id128
Instead of showing journal contents generate a new 128 bit ID suitable for identifying messages. This is intended for usage by
developers who need a new identifier for a new message they introduce and want to make recognizable. Will print the new ID in three
different formats which can be copied into source code or similar.
EXIT STATUS
On success 0 is returned, a non-zero failure code otherwise.
ENVIRONMENT
$SYSTEMD_PAGER
Pager to use when --no-pager is not given; overrides $PAGER. Setting this to an empty string or the value cat is equivalent to passing
--no-pager.
SEE ALSO
systemd(1), systemctl(1), systemd-journald.conf(5)
AUTHOR
Lennart Poettering <lennart@poettering.net>
Developer
systemd 10/07/2013 SYSTEMD-JOURNALCTL(1)