Re: [rdiff-backup-users] rdiff-backup to SOlaris machine

[Andrew Ferguson]

On Mar 6, 2009, at 5:38 AM, Pieter Donche wrote:
> I have the impression the PATH is somewhere limited to
> /usr/sbin:/usr/bin, because when I do
> # ln -s /usr/local/bin/rdiff-backup /usr/bin/rdiff-backup
> # ln -s /usr/local/bin/rdiff-backup-statistics /usr/bin/rdiff-backup- 
> statistics

So change root's $PATH, or put rdiff-backup in /usr/bin

> it finds rdiff-backup, but gives other errors afterwards:
> Traceback (most recent call last):
>  File "/usr/bin/rdiff-backup", line 20, in <module>
>    import rdiff_backup.Main
>  File "/usr/local/lib/python2.5/site-packages/rdiff_backup/Main.py",  
> line 23, in <module>
>    import getopt, sys, re, os, cStringIO, tempfile
> ImportError: ld.so.1: python: fatal: libgcc_s.so.1: open failed: No  
> such file or directory
> Fatal Error: Truncated header string (problem probably originated  
> remotely)
> Couldn't start up the remote connection by executing
> etc...
>
> probably because libgcc_s.so.1 is not searched in /usr/local/lib/ 
> libgcc_s.so.1 where is exists..

You need to adjust where Solaris is looking for shared libraries. A  
little Googling suggests you checkout the 'crle' command:
http://www.eyrie.org/~eagle/notes/rpath.html
http://bwachter.lart.info/solaris/solfaq.html
http://www.google.com/search?hl=en&q=solaris+library+path


Andrew