ke4nt1

Group: Members
Posts: 2329
Joined: Oct. 2003 |
 |
Posted: Sep. 25 2005,19:58 |
 |
It depends on WHY you , or it, wants it to be seen in /usr/sbin.
If you are looking for it to be in your default path, like it would be if it WAS in /usr/bin, you can add that location to your PATH.
If some function of the program, say some support files, really NEED to see the exec located in /usr/sbin, then you could recompile the program, to work from the /opt/exec1 directory, rather than the default /usr/sbin it was compiled to work from originally.
We would need more details about the app, to suggest to you the use of a wrapper, or other means, to have other support files follow a particular path or location. ( libs, etc.. )
If this is an extension you want to load , or install, and have it automatically run with all support files found by the app, recompiling it is the best method, combined with a wrapper, to link back into the filesystem for other lib/file support already present in the distro.
73 ke4nt
|