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.
Could you please enlighten me why I get messages like
'nvi successfully recovered smb.conf'
or the like, when I restart a crashed unix server?
(Nvi also tends to recover .pl scripts).
This seems strange for me, since I can bet these files were not opened by anyone for writing (at least I strongly hope so).
So, why they need recovery after a system crash?
nvi is a version of the vi editor - it will recover semi-edited files from unsaved sessions where the editor wasn't exited properly. i guess that means when anyone is messing around with files they can't edit, they exit vi improperly (or are cut off during a system crash), and nvi saves it in a buffer somewhere.
...that, or some cron script is using vi to update files, which i find somewhat unlikely... hmm.
i really wouldn't know what to check for. i don't think it's very likely that your system has been compromised in any way, but i'd recommend upgrading the program just to be safe. you can get the latest version here - http://www.bostic.com/vi/
nvi uses a different buffer and recovery system than vim or classic vi uses, so i'm not sure how it would act after a system crash. i think it's much more likely that the recoveries you're seeing are a result of interrupted sessions rather than anything sinister. you might want to check in your startup scripts to see if there's anything nvi uses to recover crashed sessions at startup. i found this about nvi recovery - hope it helps : http://www.neosoft.com/neosoft/man/vi.1.html#sect4