Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
About 40 minutes ago my wvdial.conf file just turned into 9 byte of linefeeds. Anyone have any idea what could have caused that to happen? It's a bit worring, hope I haven't been "owned". Knew I should have done that tripwire thingie...
I don't have any idea what happened but I have some doubts that somebody attacked you. That's because I can't imagine *why* an attacker would have any interest in your wvdial.conf file! Since it sounds like something might have glitched, it might be a good idea to check your filesystem(s). In days of old (on old RH systems before they split RHEL and Fedora), doing a
Code:
shutdown -Fr now
would reboot the system and force all filesystems to be checked on startup. You might want to check the man page to see if shutdown still works that way.
It does, at least on my box. You might also umount the partition in question and simply run (e2)fsck...
Thanks for the info. wvdial.conf is in /etc and therefore (I assumed) likely on the root partition. Also, if something in the system "glitched," I figured it would be a good idea to check all partitions. That is why I suggested the -F option with shutdown. Of course, one could overcome the "mounted partition" problem by using a live CD.
The only reason I questioned whether -F was an option is that, much to my surprise and horror, I discovered it was not an option on Ubuntu 6.10. Yet manually creating /forcefsck before reboot had the desired effect. Go figure ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.