okay, you have sbin in your path
Why is it in some paths and not in everyone's path?
I have already seen this: different PCLinuxOS flavors have different PATH setup. From one side it's understandable, because something like /usr/lib/kde4/libexec is meaningful to KDE only, from another side the lack of /sbin as appear to be the case in this thread, is questionable.
When I started using Linux many years ago the sbin directories were missing from ordinary users' paths in most distros I tried. This made sense as the executables in /sbin and /usr/sbin are there for administrative tasks and mainly intended to be run by root.
On the other hand I don't remember seeing a KDE version of PCLinuxOS where they wouldn't be found in my ordinary user's default path. This also makes sense as some of the programs in the sbin directories actually can be run by ordinary users. I don't think either solution is wrong.
That was exactly my point, I have used the terms "is questionable" meaning that "can be discussed" ... (non native English here),
I can add that several other distros are currently using /sbin and /usr/sbin in user's PATH.
[rudge12000@localhost ~]$ echo $PATH
Also, the duplicates entries like in Rudge's $PATH, IMHO aren't entirely correct ...
Any program can add to the existing path and most scripts don't check for existing entries before they add their own. Creating a new default path won't help unless you can also find and edit all the scrips that are messing with your old one. But a few duplicate entries won't matter.
... a few duplicate can affect a process performance when you run a script like:
for i in *
[example executable in /home/rudge1200/bin]
when you run a script like the above, every time the example
executable is called, the shell will search the command
in each directory listed on the PATH until will find the right directory, every time
the command is executed.
For instance the last part of Rudge's path (the final /usr/bin:/usr/sbin:/usr/lib/kde4/libexec:/bin:/sbin:/usr/X11R6/bin:/usr/games:/usr/local/bin:/usr/local/sbin) might have been added by /etc/profile.d/kde4env.sh.
Beside the performance issue, which may be ignored, PATH define also a precedence between commands, the first example that come to my mind is shutdown
that is present in /sbin and in /usr/bin and are different executables.