How did you flat out the log file ? Renamed the old log file and touch /var/log/adminlog or echo "" > /var/log/adminlog ?
If the permissions are OK, the respective applications should be able to continue writinig there.
Hey everyone
I am currently starting University, (Aus) and i am required to study Unix as apart of my study. We have gone through the basics in orientation but here at home they said i can access my files through the 'ssh' command.
All i need to know is:
- How will my wireless internet be... (2 Replies)
hi,
i have a problem and is needed by next week.
when i need to run a program at the specified time using the crontab, after that the program which will send a messege to the screen using the say command, which will show "Hello"
but there is an error when i run it, in the mail it show that
... (5 Replies)
hi !
i m in AIX box.
i wanna chk the overall CPU utilization : in % .
wat command i can try ?
i m already done with Vmstat : giving some output
iostat : not working (3 Replies)
i have been reading some atticles but i still do not understand the diferrence btw KDE & Gnome. Someone once told me he prefers Gnome to KDE 'coz of it's audio support & Redhat says ver 7.3 has KDE 3.0 & Gnome 1.4. So could someone explain? (2 Replies)
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)