x11vnc "path" to openssl doesn't match openssl location

[bigpcman]

Code: [Select]

could not find openssl(1) program in PATH.
(also checked: :/usr/bin:/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/sfw/bin)
could not find openssl(1) program in PATH.
(also checked: :/usr/bin:/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/sfw/bin)
31/01/2010 16:18:09 openssl_init: could not create or open saved PEM: (null)


Code: [Select]

tc@box2:/$ sudo find . -name "openssl"
./tmp/tcloop/openssl-0.9.8k/usr/local/openssl-0.9.8k/bin/openssl
./usr/local/openssl-0.9.8k/bin/openssl
 

[^thehatsrule^]

try something like:

Code: [Select]

export PATH="${PATH}:/usr/local/openssl-0.9.8k/bin/openssl"
x11vnc

[bigpcman]

try something like:

Code: [Select]

export PATH="${PATH}:/usr/local/openssl-0.9.8k/bin/openssl"
x11vnc

Yeah that's a good idea. I wonder if this should be added to the openssl startup script?

[Jason W]

No, that should be done if needed on an extension by extension basis.  And it would be done if needed by a wrapper script for the extension.  Installing openssl into a directory that is not in $PATH is normal, and many programs will recognize an openssl not installed into $PATH.  For those that don't, a wrapper script can be used.

[bigpcman]

No, that should be done if needed on an extension by extension basis.  And it would be done if needed by a wrapper script for the extension.  Installing openssl into a directory that is not in $PATH is normal, and many programs will recognize an openssl not installed into $PATH.  For those that don't, a wrapper script can be used.

OK that makes sense.
So the x11vnc.tcz extension should be remade with a wrapper script.

[robc]

the x11vnc extension does have a wrapper script. The script is x11vnc in /usr/local/bin, this is the script:

Code: [Select]

#!/bin/sh
export LD_LIBRARY_PATH=/usr/local/openssl-0.9.8k/lib
/usr/local/bin/x11vnc-bin "$@"
I haven't had trouble before using this kind of script before  between the 0.9.8h and 0.9.8k openssl extensions.
I can add a PATH adjustment to the wrapper if that will clear this bug up.

[bigpcman]

the x11vnc extension does have a wrapper script. The script is x11vnc in /usr/local/bin, this is the script:

Code: [Select]

#!/bin/sh
export LD_LIBRARY_PATH=/usr/local/openssl-0.9.8k/lib
/usr/local/bin/x11vnc-bin "$@"
I haven't had trouble before using this kind of script before  between the 0.9.8h and 0.9.8k openssl extensions.
I can add a PATH adjustment to the wrapper if that will clear this bug up.

It would also be nice to have a start,stop restart capability like dropbear and samba services. The start command would of course have to include the "use the configuration file option".

[robc]

the x11vnc extension does have a wrapper script. The script is x11vnc in /usr/local/bin, this is the script:

Code: [Select]

#!/bin/sh
export LD_LIBRARY_PATH=/usr/local/openssl-0.9.8k/lib
/usr/local/bin/x11vnc-bin "$@"
I haven't had trouble before using this kind of script before  between the 0.9.8h and 0.9.8k openssl extensions.
I can add a PATH adjustment to the wrapper if that will clear this bug up.

It would also be nice to have a start,stop restart capability like dropbear and samba services. The start command would of course have to include the "use the configuration file option".

I'll look into this but I don't have the time at the moment to get this done. I may later this week.

[^thehatsrule^]

Noting the wrapper script in the .info might be helpful.