-   Linux - Networking (
-   -   wvdial.conf vanished (

senseproof 05-09-2009 05:31 PM

wvdial.conf vanished
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...

blackhole54 05-10-2009 11:27 PM

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


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.

JZL240I-U 05-11-2009 06:56 AM

It does, at least on my box. You might also umount the partition in question and simply run (e2)fsck...

blackhole54 05-11-2009 07:33 PM


Originally Posted by JZL240I-U (Post 3536935)
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 ...

JZL240I-U 05-12-2009 04:52 AM

You're right with the mounted /etc, I overlooked that. But as I wrote, on SuSE -F works like it always did.

All times are GMT -5. The time now is 12:28 AM.