I have a program that does not install its executables to one of the locations in the standard path. It is a custom module for a custom box, so I can not modify it easily.

When I manually move or link the executable to /usr/bin (and other directories in the path), the files works and is found when called, as I want.

HOWEVER, when I restart the system the file or link disappears. Somehow its gets deleted during restart.

I use it through an SSH shell, again a custom module with inbuilt path, so I can not play with the compiled in path.

I NEED a way to properly copy the file to one of the directories in the path and let the system know it is valid and to LEAVE IT ALONE.

Has anybody got ideas on where and what for should I look?

Thanks

why dont you just add the path where the executable is to your path variables in the home dir of the user you ssh in as??



ie

assuming you are using bash,

in .bash_profile, add a line

... because the daemon has an incompiled path setting. Namely it has a standard set of path compiled in, but does not read the user paths. As I said I am starting an ssh shell for remote backups.

There is a way to force the daemon to read users settings from their home directory, but this is not an acceptable solution in this case because:

1. It is a security risk, as the settings pertain to more than just paths.

2. It has to be done for each user everytime there is a user.

I've had a similar problem before with a different program, on a different machine (Fedora Core 5, a little old... ), so I would rather work out what is behind all this. The current machine is a Thecus RAID box.

I copy all files as root, so as far as I know they should remain where I put them. My guess is it is some kind of security feature/bug... and ther has to be a way around as after all packages installed by rpm have no troubles.

I was hoping somebody else noticed something similar.