04-04-2003
Interesting, thanks.
Can you post a few lines of the recent logfile showing the faxmodem entries?
Thanks, N
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Platform sol 8
I had wtmpx growing very large(1.2 G). I copied the file and compressed it the did a "cat /dev/null > /var/adm/wtmpx" to zero out the file and not close any doors to any processes. (After searching this seemed like the right method)
This is a box that gets accessed from other... (5 Replies)
Discussion started by: finster
5 Replies
2. UNIX for Dummies Questions & Answers
i accedently "deleted" all workspaces
I have a black screen and dont know what to do
solaris common desktop enviroment (1 Reply)
Discussion started by: ssshakir
1 Replies
3. UNIX for Advanced & Expert Users
Do someone know how to delete entry(some lines)
in file "wtmpx" that command "last" use it.
this file is binary so I cannot edit directy.
=========================
#last
root pts/1 noc Fri Mar 3 22:04 still logged in
root pts/1 noc Fri Mar 3 22:01 - 22:02 ... (4 Replies)
Discussion started by: arm_naja
4 Replies
4. UNIX for Dummies Questions & Answers
Hello everybody:
the wtmpx file on my Sol8 machine, got so big (2GB), that my root partition is almost full now, can I empty that file, I read about it that it contains database of user access and auditing, so in case I emptied it will it affect my system??
Thanks alot (3 Replies)
Discussion started by: aladdin
3 Replies
5. Solaris
Hi,
I am using Sun Solaris 5.9 OS. I have found a file called wtmpx having a size of 5.0 GB. I want to clear this file using :>/var/adm/wtmpx. My query is, would it cause any problem to the running live system.
Could anyone suggest the best method to clear the file without causing problem to... (6 Replies)
Discussion started by: Vijayakumarpc
6 Replies
6. UNIX for Advanced & Expert Users
Hi
in my solaris 9 system wmptx file is not updating so it is not recording any login or logout or any other entry.
can any one tell me how to solve this problem (0 Replies)
Discussion started by: aaysa123
0 Replies
7. Solaris
What could possibly happen if wtmpx file got deleted by mistake?
Thanks, (8 Replies)
Discussion started by: Pouchie1
8 Replies
8. Solaris
Hi All
I work on solaris 8, 9 and 10 platforms and have encountered an error which is my wtmpx files appear to be corrupted as all entries contain the date 1970 (the birth of unix).
Now this is obviously not the case, so my query is:
1 - Can the existing wtmpx files be manipulated to... (6 Replies)
Discussion started by: drestarr96
6 Replies
9. Solaris
Hi, saw couple threads about wtmpx corruption, I had this problem on many servers, last command was not working or displaying old output, found good information on a thread on this site and wrote a perl script to fix, thought it might help some people.
I found that using wtmpfix I lost many... (0 Replies)
Discussion started by: yannm
0 Replies
10. UNIX for Advanced & Expert Users
Hi,
I tried running the command "last" in the server to check the users that were last logged into the system.
However, I get this error :
root@csidblog:# last
/var/adm/wtmpx: Value too large for defined data type
How do I proceed to get this info?
I read some forums suggesting to use... (2 Replies)
Discussion started by: anaigini45
2 Replies
LEARN ABOUT DEBIAN
logtail2
LOGTAIL(8) logtail2 manual LOGTAIL(8)
NAME
logtail2 - print log file lines that have not been read
SYNOPSIS
logtail2 [-t] -flogfile [-ooffsetfile]
DESCRIPTION
logtail2 reads a specified file (usually a log file) and writes to the standard output that part of it which has not been read by previous
runs of logtail2. It prints the appropriate number of bytes from the end of logfile, assuming that all changes that are made to it are to
add new characters to it.
logfile must be a plain file. A symlink is not allowed.
logtail2 stores the information about how much of it has already been read in a separate file called offsetfile. offsetfile can be omit-
ted. If omitted, the file named logfile.offset in the same directory which contains logfile is used by default.
If offsetfile is not empty, the inode of logfile is checked. If the inode is changed, logtail2 uses the heuristics stored in
/usr/share/logtail/detectrotate/ to find a file that might be the rotated logfile and prints it starting with the stored offset. It then
proceeds to simply print the entire new file and generates a new offsetfile. If the inode is not changed but logfile is shorter than it
was at the last run of logtail2, it writes a warning message to the standard output.
OPTIONS
-f logfile to be read after offset
-o offsetfile stores offset of previous run
-t test mode - do not change offset in offsetfile
RETURN VALUES
0 successful
65 cannot get the size of logfile
66 general file or directory access issue
73 cannot write offsetfile
AUTHOR
The original logtail was written in C by Craig H. Rowland <crowland@psionic.com>. This version of logtail is a modification of Paul Sloot-
man's re-implementation in perl. enhanced by the Debian Logcheck Team <logcheck-devel@lists.alioth.debian.org>.
This manual was written by Oohara Yuuma <oohara@libra.interq.or.jp> and enhanced by the Debian Logcheck Team
<logcheck-devel@lists.alioth.debian.org>..
SEE ALSO
logcheck(8)
Debian 28 Jul 2007 LOGTAIL(8)