You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Thursday, November 17th 2005, 10:53pm

Session Management Problem?

I'm sure this is a stupid question but I'm going to ask it anyway. I have just installed Fedora core 4 and have run into situations where I have manually edited and file on the command line (for example hosts or resolv.conf), saved it and then issued a "shutdown-r now" and when i get logged back in and look at the file it is back the way it originally was (before my edits).

Can someone explain what is going on and how I can make my changes permanently stick?

Thanks - [trying to convert to Linux but cant quite make it]

2

Tuesday, November 22nd 2005, 7:50pm

RE: Session Management Problem?

Intrigating...


Give more details. Vi? Have you edited it as root?

3

Wednesday, November 23rd 2005, 9:21pm

Yes I have.. it still reverts when I re-boot the box..
This sux..

4

Thursday, November 24th 2005, 12:49pm

I can guess no much from your problem without further details.

The possibilities I see are:

i. You are not effectively writing your files to disk (wrong permissions?).
ii. You are writing, but in the wrong place.
iii. There is a new and revolutionary safety mechanism in Fedora for system stability assurance, shamefully plagiarizated from Rwindows XP that backs up your configurations and puts them back to its places when restarting... Mourning.


Please tell us somthings like:

It happens when using another editor?
It allways happens or sometimes?
It happes for files anywhere or in a specific place(s)?
Have you run any Redhat tools meanwhile? It would explain a lot of things.
Did you notice any abnormal messages in you system (dmesg)? Unmounting problems can lead to unflushed data.

This post has been edited 1 times, last edit by "javmss" (Nov 24th 2005, 12:49pm)


5

Monday, November 28th 2005, 10:17pm

1) I use vi to edit the files.. and it saves ok (again i can see the changes after i log off, but when i reboot they revert back)
2) It happens all the time
3) Even if i use the redhat/kde gui to change lets say the DNS server it reverts when I reboot..
4) No abnormal mesasges in dmesg (and I do a kde reboot)

Thanks

6

Tuesday, November 29th 2005, 6:14pm

It seems that the iii and most unbelievable choice is the really one.

Is there any non-standard services running at startup?
Did you try to grep your old configurations? I mean grep your old IP in the /etc to see if any redhat tool is also storing this data for a possible recovering after reboot or something like.
If your computer replaces your old configuration, it must be somewhere, don´t you agree?

If you try to change your configurations using RH tools, the reboot problem does not happen, right?
I don´t like the customized tools bond to Linux distros, and that made me to avoid RH. The kind of trouble you have is not rare, as the companies feel ease to do non-standard things in the system.
The best you do is to tame your distro. As the time passes, you learn to live with its oddities.

By now. Make this try. Search the whole root if needed.