10-09-2003
Yes you have allowed the file to get too large. There are ways to view it like using "more" and page and tail/head... Also there is a command called split, that might work for you. I would try to copy it and then manipulate the copy to try and break it up.
To simply zero out the file type "> filename" this uses the cat redirect to input "null" to the file thus overwriting any data in the file.
However, most folks dont like to do that... I would suggest setup a cron to copy/move and compress log files so that they never get too large. The frequency depends on how fast they grow. I would start with a monthly cron at first.
cp log.orig log.bak.<date>
compress log.bak.<date>
> log.orig
9 More Discussions You Might Find Interesting
1. AIX
USERS="me you jim joe sue"
for user in ${USERS}; do
rmuser -p $user
usrdir=`cat /etc/passwd|grep $user|awk -F":" '{ print $6 }'`
rm -fr `cat /etc/passwd|grep $user|awk -F":" '{ print $6 }'`
echo Deleting: $user '\t' REMOVING: $usrdir
done
This is for AIX ONLY!!! but easily ported to... (0 Replies)
Discussion started by: Optimus_P
0 Replies
2. UNIX for Dummies Questions & Answers
I wish to clean a text file of the following characters
1/2, 1/4, o (degrees)
I cant display these characters. I have tried ALT+189 etc (my terminal emulator is set to ASCII). How do I display the above ? I am using HP UX 10. (5 Replies)
Discussion started by: ferretman
5 Replies
3. UNIX for Dummies Questions & Answers
Hi everybody,
I have been given a task to find the names of some products that can clean up databases by removing confidential information. The situation is that a client imports data from public sources (government websites, etc.) but that this data sometimes includes things like Social... (0 Replies)
Discussion started by: rhfrommn
0 Replies
4. Shell Programming and Scripting
Hi,
I am facing problems while trying to clean a log file(Means making its file Size zero).
I am not the owner of this file. From the command line, I can clean it by becoming a Sudo. (">logfilename").
I want to automate it using perl. But inside a script, sudo somehow doesnt seem to work. ... (1 Reply)
Discussion started by: jyotipg
1 Replies
5. UNIX for Dummies Questions & Answers
Hello *!
Just a short question. Where on the system i can find core files. I have one SUN server (Solaris 8) and from time to time I must clean core files on it. But i am not sure where i can find those files. Thank you in advance. :) (5 Replies)
Discussion started by: ghost01
5 Replies
6. Shell Programming and Scripting
HI ,
I am getting the source data as below.
Source Data
CDR_Data,,,,,
F1,F2,F3,F4,F5,F6
5,5,6,7,8,7
6,6,g,,,
7,7,76,,,
8,8,gt,,,
9,9,df ,d,d,d
,,,,, (4 Replies)
Discussion started by: wangkc
4 Replies
7. Shell Programming and Scripting
Hi,
I have a file with multiple rows. each row has 8 columns.
Column 8 has entries separated by commas. I want to exclude all the rows in which column 8 has more than 3 commas.
1234#0/1 - ABC_1234 3 ATGCATGCATGC HHHIIIGIHVF 1 49:T>C,60:T>C,78:C>A,76:G>T,65:T>G
Thanks,
Diya (3 Replies)
Discussion started by: Diya123
3 Replies
8. Shell Programming and Scripting
I am trying to cleanup a directory with around 4000 files, and using the below command to delete all .gz files older than 60 days, I am having the same issue of arguments being too long. is there a way i can use the same command to do what I intend to do.
find /opt/et/logs/Archive/*.log.*.gz... (4 Replies)
Discussion started by: Shellslave
4 Replies
9. Shell Programming and Scripting
Hi,
I have OCR'ed text that needs cleaning.
Lines are delimited by parts of speech (POS), for example,
each line will have either an
adj. OR s. f. OR s. m. etc
I need to uppercase all text before the POS
but all text within parentheses to be lowercase
Text after (and including) the POS... (6 Replies)
Discussion started by: safran
6 Replies
LEARN ABOUT MOJAVE
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)