Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
1) When I cat the file I can see all info inside. (to current time)
2) When I tail the file (tail -f ) I don't see the end of the file. Last info inside the file is a few days/hour old.
3) But if I do a ls -l it has the current date/time (file is being updated)
4) When I VI the file I cant go to the end of the file and get this message just as I open the file "file.log [noeol] 2444996L, 190001152C "
I have restarted the process and it fixes it for a while, but hen start acting like this again.
I cant restart the linux server as its in production (probably only in 2 weeks )
Any idea what it could be ? All other log files seems ok
Looks like buffering; all programs do this to some extent, and if the log file isn't being written to often, it (tail -f) can appear to be 'behind the curve'
Similarly, if the file is open and being written to, then it may well have 'noeol' = no end-of-line char.
Nothing to worry about.
According to the output, that's 2.4 million lines
Hi thanks for the reply's I found the problem, it was a mount point that was 100% full although a different process that was started up as root user could still write to same mount point. That lead me to believe it was an process/application issue.