09-27-2007
Just beat me to it! Was going to give almost exactly the same answer. BTW, since you said to correct your English, I did fix a spelling mistake in your post. Hope you don't mind.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Ok, lets suppose I have two files like so:
file1
John 5441223
Sandy 113446
Jill 489799
file2
Sandy Tuesday
Jill Friday
John Monday
Is it possible to match records from these two files and output them into one output file? For example, lets suppose I want to output like this:
... (5 Replies)
Discussion started by: Liguidsoul
5 Replies
2. Shell Programming and Scripting
Well I have a 3000 lines result log file that contains all the machine data when it does the testing... It has 3 different section that i am intrsted in
1) starting with "20071126 11:11:11 Machine Header 1"
1000 lines...
"End machine header 1"
2) starting with "20071126 12:12:12 Machine... (5 Replies)
Discussion started by: vikas.iet
5 Replies
3. Shell Programming and Scripting
OS : Linux 2.6.9-67 - Red Hat Enterprise Linux ES release 4
Looking for a script that reads the following log files that gets generated everynight between 2 - 5am
Master_App_20090717.log
Master_App1_20090717.log
Master_App2_20090717.log
Master_App3_20090717.log... (2 Replies)
Discussion started by: aavam
2 Replies
4. Shell Programming and Scripting
Hello
Can someone help me to write a perl script or kornshell reading a two files and outputting to comma format.
Here is the two files
listofdisks.txt
id, diskname, diskgroup, diskisze(GB), FC
1, CN34, GRP1, 30, FC_CN34
2, CN67, GRP5, 19,
4, VD1, GRP4, 23, FC_VD1
6, CF_D1, ... (0 Replies)
Discussion started by: deiow
0 Replies
5. UNIX for Dummies Questions & Answers
Solaris 10/Korn
Hi unix experts!,
Is it possible to output the actual file names to a file as they are being deleted via the rm command?
Context:
Im executing the shell script at the command line and directing the output to an output file eg purgescript.ksh > output.lst
within the... (3 Replies)
Discussion started by: satnamx
3 Replies
6. Shell Programming and Scripting
Hi,
I have a shell script
#!/bin/sh
date
echo 'HI PROD'
echo $Please ENTER THE INPUT 1 for old files 2 for new file
read i
if ;
then
cd /apps/acetp3_logs/prod3/O*
pwd
echo $PLEASE ENTER THE STRING TO SEARCH (PLEASE ENTER THE STRING INSIDE QUOTES ' ')
read j
echo... (6 Replies)
Discussion started by: thelakbe
6 Replies
7. UNIX for Dummies Questions & Answers
I have many files that can have various amounts of rows. I essentially want to output each row into a new file if a pattern is matched between two files.
I have some code that does something similar but I want it to output every single input row from every file into a separate output file; that... (5 Replies)
Discussion started by: verse123
5 Replies
8. UNIX for Beginners Questions & Answers
I have two files:
File_1:
@M04961:22:000000000-B5VGJ:1:1101:9280:7106 1:N:0:86
GGCATGAAAACATACAAACCGTCTTTCCAGAAATTGTTCCAAGTATCGGCAACAGCTTTATCAATACCATGAAAAATATCAACCACACCAGAAGCAGCAT
+
GGGGGGGGGGGGGGGGGCCGGGGGF,EDFFGEDFG,@DGGCGGEGGG7DCGGGF68CGFFFGGGG@CGDGFFDFEFEFF:30CGAFFDFEFF8CAF;;8F
... (3 Replies)
Discussion started by: Xterra
3 Replies
9. Shell Programming and Scripting
Good Morning,
Every so often, I have copy scripts that to don't complete, but I don't immediately know why. It usually ends up being a permissions issue or a length issue.
The scripts edit a log file, so I'd like to include any copy errors/issues in that file to check if the copies... (4 Replies)
Discussion started by: Stellaman1977
4 Replies
10. Shell Programming and Scripting
I have a log file that looks like this. the lines are grouped. 2 lines per entry.
M: 2019-01-25 13:02:31.698 P25, received network transmission from KI4EKI to TG 10282
M: 2019-01-25 13:02:35.694 P25, network end of transmission, 4.3 seconds, 1% packet loss
M: 2019-01-25 13:02:38.893 P25,... (7 Replies)
Discussion started by: ae4ml
7 Replies
LEARN ABOUT DEBIAN
xfs_logprint
xfs_logprint(8) System Manager's Manual xfs_logprint(8)
NAME
xfs_logprint - print the log of an XFS filesystem
SYNOPSIS
xfs_logprint [ options ] device
DESCRIPTION
xfs_logprint prints the log of an XFS filesystem (see xfs(5)). The device argument is the pathname of the partition or logical volume con-
taining the filesystem. The device can be a regular file if the -f option is used. The contents of the filesystem remain undisturbed.
There are two major modes of operation in xfs_logprint.
One mode is better for filesystem operation debugging. It is called the transactional view and is enabled through the -t option. The
transactional view prints only the portion of the log that pertains to recovery. In other words, it prints out complete transactions
between the tail and the head. This view tries to display each transaction without regard to how they are split across log records.
The second mode starts printing out information from the beginning of the log. Some error blocks might print out in the beginning because
the last log record usually overlaps the oldest log record. A message is printed when the physical end of the log is reached and when the
logical end of the log is reached. A log record view is displayed one record at a time. Transactions that span log records may not be
decoded fully.
OPTIONS
-b Extract and print buffer information. Only used in transactional view.
-c Attempt to continue when an error is detected.
-C filename
Copy the log from the filesystem to the file filename. The log itself is not printed.
-d Dump the log from front to end, printing where each log record is located on disk.
-D Do not decode anything; just print data.
-e Exit when an error is found in the log. Normally, xfs_logprint tries to continue and unwind from bad logs. However, sometimes it
just dies in bad ways. Using this option prevents core dumps.
-f Specifies that the filesystem image to be processed is stored in a regular file at device (see the mkfs.xfs(8) -d file option).
This might happen if an image copy of a filesystem has been made into an ordinary file with xfs_copy(8).
-l logdev
External log device. Only for those filesystems which use an external log.
-i Extract and print inode information. Only used in transactional view.
-q Extract and print quota information. Only used in transactional view.
-n Do not try and interpret log data; just interpret log header information.
-o Also print buffer data in hex. Normally, buffer data is just decoded, so better information can be printed.
-s start-block
Override any notion of where to start printing.
-t Print out the transactional view.
SEE ALSO
mkfs.xfs(8), mount(8).
xfs_logprint(8)