Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About flundy

  • Rank
    Occasional Forum Poster
  1. Works well for me, but my linux clients are very simply structured. You might have some issues with symlinks across filesystems. Get the latest update to Retrospect7, as I belive it handles unix clients a little better than the base release.
  2. I have the same problem-- Retrospect7 is continually asking for new media even though my disk device is 60-75% empty. Giving it another filename on the same disk allows things to continue. This is *not good* for automating backups. I am using 7.0.265 on Win2k SP4 on NTFS.
  3. flundy

    Unix client install

    Solaris has a 10yr product lifecycle-- that's Solaris' selling point. SunOS 5.7 support is terminates in 2008, I believe. Solaris7 is still viable, but I would recommend the newer versions instead. Now, whether Dantz chooses to support Solaris7 is something else entirely... http://www.sun.com/software/solaris/releases.xml http://www.sun.com/software/solaris/lifecycle.xml
  4. flundy

    Solaris install of client

    There is a little more work to do w/ the RedHat and Solaris clients. On my clients, I have to do the following after doing the pkgadd or rpm: 1) Solaris 9 requires a pair of symlinks: ln -s /usr/sfw/lib/libglib-1.2.so.0 /usr/lib ln -s /usr/sfw/lib/libgthread-1.2.so.0 /usr/lib 2) #!/bin/sh needs to be added to /usr/local/dantz/client/rcl 3) Symlinks need to be added to make the startup script conform to the rest of the box: ln -s /usr/local/dantz/client/rcl /etc/init.d/retroclient ln -s /etc/init.d/retroclient /etc/rc3.d/S99retroclient I passed this back to EMC/Dantz-- hopefully these chgs will make it on the next client release.