Solved I think that I have met my match

[CShell]

Okay, now things are really getting weird. Below is what I'm now getting.

Each time you sign out and back into your desktop -- you will get a "new" dbus process. It's respawned each time you login.

Not sure why you are concerned about this? . A lot of Unix processes work this way.

 

[Cedric62]

Each time you sign out and back into your desktop -- you will get a "new" dbus process. It's respawned each time you login.

Not sure why you are concerned about this? . A lot of Unix processes work this way.

okay, I wasn't sure about that.

Also, the reason why I became concerned, was because it appeared to me that every few days, /etc/rc.d/dbus kept getting reset to non-executable. Also, it appeared that whenever this would happen, then my system would act slightly unstable, and maybe certain desktop programs would not launch, or would occasionally stop responding. Also, the problems would typically seem to go away after I used chmod to make dbus executable again.

However, I freely admit that a lot of problems are somewhat self inflicted, and maybe I'm not the best at correctly interpreting what I'm seeing on my screen, and for the moment at least, dbus hasn't flipped back to being non-executable, and for the time being my system seems stable and reliable.

 

[Cedric62]

okay, I wasn't sure about that.

Also, the reason why I became concerned, was because it appeared to me that every few days, /etc/rc.d/dbus kept getting reset to non-executable. Also, it appeared that whenever this would happen, then my system would act slightly unstable, and maybe certain desktop programs would not launch, or would occasionally stop responding. Also, the problems would typically seem to go away after I used chmod to make dbus executable again.

However, I freely admit that a lot of problems are somewhat self inflicted, and maybe I'm not the best at correctly interpreting what I'm seeing on my screen, and for the moment at least, dbus hasn't flipped back to being non-executable, and for the time being my system seems stable and reliable.

So, I think that what might have been happening is that whenever I happened to restore my installation using rsync, then the version of dbus stored at at /etc/rc.d/dbus wasn't being restored with the correct file attributes, and I'm guessing that is why dbus kept become non-executable. I don't feel like testing this theory by doing a fresh reinstall and a restore, but if I have to do so again in the future, I'll be sure to check to see if dbus is executable or not, before I do anything else. So far, no problems since the last time I used chmod to reset dbus as executable.