[X2Go-Dev] x2go no longer works after reboot on CentOS 6.4
Jan Engelhardt
jengelh at inai.de
Mon Jun 10 13:32:09 CEST 2013
On Monday 2013-06-10 12:46, Mike Gabriel wrote:
>>
>> As a note of interest, /usr/libexec/x2go is the correct directory it seems:
>>
>> However, there are also files in /usr/lib64/x2go/
>>
>> [root at local ~]# LC_ALL=C ls -al /usr/lib64/x2go/
>> total 72
>> drwxr-xr-x. 2 root root 4096 Jun 6 13:28 .
>> dr-xr-xr-x. 49 root root 36864 Jun 6 19:49 ..
>> -rw-r--r--. 1 root root 20852 May 19 01:02 x2godbwrapper.pm
>> -rw-r--r--. 1 root root 1834 May 19 01:02 x2gologlevel.pm
>> [root at local ~]#
>
> All those files should be in the same folder.
> The folder should be echoed to stdout by this command:
>
> x2gopath libexec
>
I am in an undecided state on that.
System Perl modules also live in an *arch-dependent* directory (e.g.
/usr/lib/perl5/5.16.0/x86_64-linux-thread-multi) because they can
have arch-specific native code. As such, placing .pm files into an
arch-specific x2go path (/usr/lib64/x2go satisfies this on current
RH/SUSE) is a safe choice.
This is also why the x2go perl scripts use `x2gopath lib`
and not `x2gopath libexec`.
More information about the x2go-dev
mailing list