/sbin/fixfiles onboot
 

I was trying to fix another problem on my Centos 6.5, 64 bit system.

I ran the commsnd

sbin/fixfiles onboot

then I rebooted it was a huge mistake I got the message.

I simply do not want this.

How do I shut it down?

The command's operation manifests itself as a string of asterisks on the command line.

They are hard to get rid of.

How do stop this?

Any help appreciated. Thanks in advance.

R.

jyunker

Then first of all you should find out why the hell you choose to run 'fixfiles' for trying to fix a completely unrelated problem? I mean how effective can computing be if you just go ahead and run all sorts of commands without knowing their effects or consequences?

Now there's three ways around this: face the consequences of the mistakes you made (painful as it is at least it teaches you something) or disable SELinux altogether (at which point you probably shouldn't run RHEL, CentOS, Fedora or derivatives) or, wrt your original problem, follow advice already posted there (no need to rehash that). Relabeling doesn't take that long so I'm not sure why you wouldn't just go ahead with it...

This is why I used said command
 

The problem that you refer to here as the original problem has been fixed satifactorily. I simply made a perl script used my Cents 6.5, 64 bit, LiveDVD and ran the perl script comparing my LiveDVD file permissions against the one on my installed 6,5, 64 bit. As you said I cannot be sure that this will work, but I have been scanned many times since the repair and I am still on the network. I must be doing something correctly; it is not a perfet solution, but it works for now.

The issue that I am referring to here is different. The command that I used can be found here.

http://www.linuxquestions.org/questi...rectly-777921/

The reference that I used is at the fourth post. My problem seems to be exactly what the one is in the initial post. I only tried this after having tried many other things.

So that is why I used the command in question, I wanted to fix a similar problem.


I just thought that I would explain.


Let me be sure, you said to let it continue SELinux label routine and then deactivate it once SELinux labels are installed.

Thanks in advance.

R,

jyunker

So you get an error message that reads "The configuration defaults for GNOME Power Manager have not been installed correctly"?


Ah, so it isn't "exactly what the one is in the initial post"?


Can you understand how inefficient this all is? It would have been way easier if your initial post contained a description of your problem and what you actually and exactly tried to do to fix this.