Hi,
I am running my script using nohup, but I am not able to capture the log file for that process could naybody please help...
Here is what I am doing....
nohup ./script & 1>/home/user1/log.txt
but I am not able to capture the log.....Is there anyother way I can capture the log... (2 Replies)
Hi ,
I have seen some log files where they have captured the command that is being executed, comments present in the scripts and the out put of the command as well, through scripts. could any one of you please let me know how do i do that?
Thanks in advance.
Cheers,
Waseem (4 Replies)
Hello,
If I run a program from within shell, the output is displayed in the command line terminal. Is there a way I can capture that output and choose only the very last string in it to send it to a new file?
Thank you (6 Replies)
Hi
I have a script that will run multiple unix & sql commands. I want to see the output as well as capture it to a log file for further analysis. Is there an easy way to do that instead of adding "tee -a logfile" on everyline or even on the execute line (i.e. script | tee -s logfile).
Thanks (1 Reply)
Hi,
I wanted to know how i could accomplish this in a script using ksh.
Lets say there is a file called test.dat and it has a certain input like below :
.
.
Hi = 56
Hi = 67
.
.
1 record(s) selected
Now i need to capture the numbers after the = sign and store them in a... (3 Replies)
Hi
I have a requirement to write a script to capture all errors in a Logfile and send the file in email.
If there is any error occurred the subject of email will be ERROR , If there are no error occurred the subject of email will be SUCCESS.
So I created a Log file and put the Appropriate... (2 Replies)
Hi,
as the title says, I am after a simple script, which will open the Alert log from
an 11.2.0.1 Linux environment and mail the error message and description to a recipient email address.
I can then schedule this job via cron and let it run every 15 minutes.
I have searched online... (16 Replies)
Hi all,
My file :test.txt just like this:
...........................
From: 333:123<sip:88888888888@bbbb.com
To: <sip:123456@aaaaa.com
.........................
I want a script to capture the string between sip: & @
Expect output:
88888888888
123456
Please help! (4 Replies)
Dear All
From below mention input file I want op file as mention. Kindly help.
IP file:
"BSCGNR4_IPA17_C" 329 140119 0717 RXOCF-105 KJO001_BASC_NG AC FAULTY DG ON DOOR OPEN
Needed OP:
140119 0717 KJO001_BASC_NG AC FAULTY DG ON DOOR OPEN
Note that string mark in red as variable in... (3 Replies)
Hi
I have a system running uname -a
Linux cmovel-db01 2.6.32-38-server #83-Ubuntu SMP Wed Jan 4 11:26:59 UTC 2012 x86_64 GNU/Linux
I would like to capture the contents of /var/log/syslog from 11:00AM to 11:30AM and sent to this info via email.
I was thinking in set a cron entry at that... (2 Replies)
Discussion started by: fretagi
2 Replies
LEARN ABOUT OSX
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)