In the past when I tried to use a form of relative path, or a variable it did not seem to include the path properly. I will try to retest this against 1.92 and put a fix in place for that build as 1.93. It will require to load the config settings prior to calling the use on various perl modules.
The easiest work around would to be to link the following directory
mkdir opt
and then
ln -s /opt/Inprotect to where ever the correcsponding inprotect directory is
to fake the hard coded path else edit each file in 1.00 but if you do that any updated scripts that would come out would needed edited.
I recommend to link the directory if your system does not contain / or wish to contain /opt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm running this off a LiveCD so portions of the filesystem are read-only (like /opt). That's why I installed it under a different directory that was writeable.
I did finally put in a workaround.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In the past when I tried to use a form of relative path, or a variable it did not seem to include the path properly. I will try to retest this against 1.92 and put a fix in place for that build as 1.93. It will require to load the config settings prior to calling the use on various perl modules.
The easiest work around would to be to link the following directory
mkdir opt
and then
ln -s /opt/Inprotect to where ever the correcsponding inprotect directory is
to fake the hard coded path else edit each file in 1.00 but if you do that any updated scripts that would come out would needed edited.
I recommend to link the directory if your system does not contain / or wish to contain /opt
I'm running this off a LiveCD so portions of the filesystem are read-only (like /opt). That's why I installed it under a different directory that was writeable.
I did finally put in a workaround.