in reply to Solaris Thread Problem

Ive been bangin away on Solaris for a few years now. Getting functionality is fairly easy nowadays via the packages off of sunfreeware.com. Getting all the functionality you need, or optimizations you need isn't easy nor painless yet, and I doubt will be in the forseeable future. Simply due to the breadth of Sun's customer base. Since the threading is still considered 'beta' (someone correct me if im wrong there) they more than likely wont roll it out on their enterprise OS.

Moral of the story: once bitten twice shy. I have found it better when rolling something out for devel or production on a Solaris system, if that something isn't directly built into the OS, to grab the software from the originating source and recompile. Then build my own package to distribute to client hosts.

On a side note if anyone can get Net::SSH::Perl to install (with all dependancies) and run 100% consistantly on Solaris 2.7 -> 2.9 I would love to hear how you did it. I attempted it and my code would die, gathering entropy, opening devices, all sorts of whacky stuff, but on Linuxs and FreeBSD module works great.

/* And the Creator, against his better judgement, wrote man.c */

Replies are listed 'Best First'.
Re: Re: Solaris Thread Problem
by vek (Prior) on Feb 06, 2003 at 13:28 UTC
    I've had Net::SSH::Perl running on a 2.7 box for a while now. It was a pre-requisite for Net::SFTP which I use heavily. As I recall, Net::SSH::Perl was a bit of a pain to install (because of all the dependancies) but once installed I haven't run into any issues. Are you having problems with the install or with getting your code to work?

    -- vek --
      Getting the code to run consistantly. It runs sometimes, and fails other times. If it failed the same way it wouldn't be an issue, but it doesn't. Sometimes is cant collect entropy from /dev/random, or /dev/egd-pool (I have tested both with EGD running, as well as patching the kernel to provide native entropy), other times it fails creating the socket, other times it runs great for 3 hosts and will just die on the 4, etc.. If you turn around and run the code again as soon as it dies, sometimes it works all the way through, other times it will fail earlier, etc..

      The absolute worse kind of problem. I simply ported the functoinality over to a FreeBSD box, and things are happy now, but I hate not know why it won't run.

      /* And the Creator, against his better judgement, wrote man.c */

        i also found it a pain to build for 2.8, but once built and Net::SSH::Perl gotcha! was discovered i haven't had any problems.

        ensure that your openssl is built with the same compiler as your perl, i think Net::SSH::Perl's Makefile.PL complains if it isn't. YMMV