ClusterSSH / Leopard Fix

[Neil Getker]

I posted a thread on here awhile ago, detailing problems with  
ClusterSSH and Leopard.

I found a solution a few days later, but never posted it.  Someone  
emailed me a couple of days ago
so here is the solution for all, enjoy.

 From either an upgrade or a clean install of Leopard:

(If old caches exist from a upgrade, remove from /var/cache)

Install All SDK/XCODE 3.0 Tools.

After that, from a Terminal:

sudo /usr/bin/perl -MCPAN -e shell

install CPAN::Bundle

(wait too fucking long)

force install Tk
force install X11::Protocol

After that, download clusterssh from http://sourceforge.net/project/showfiles.php?group_id=89139

untar, cd into dir

sudo perl -f Makefile

This will install it to /usr/local/bin/

WOAH NELLY!  Don't run it yet, won't work.

You need a few things leopard doesn't install by default that tiger did:

An xinitrc, copy the system default from:

cp /usr/X11/lib/X11/xinit/xinitrc ~/.xinitrc

A bashrc to set ur enviornment variables.

Here is mine:

source /etc/profile
DISPLAY=127.0.0.1:0.0;export DISPLAY


Now, you can run X11 and you should see a normal prompt in xterm, not  
the weird bash 3.21#

And just running cssh or whatever works fine.


-Neil
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo/macports-users

[Jochen Küpper]

On 15.01.2008, at 19:03, Neil Getker wrote:

> DISPLAY=127.0.0.1:0.0;export DISPLAY


Doesn't Leopard start X11 on demand via launchd via an corresponding  
socket in the DISPLAY variable?
You are just defeating that...

Greetings,
Jochen
--
Einigkeit und Recht und Freiheit                http://www.Jochen-Kuepper.de
     Liberté, Égalité, Fraternité                GnuPG key: CC1B0B4D
         Sex, drugs and rock-n-roll




_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo/macports-users

[David Blank-Edelman]

> I posted a thread on here awhile ago, detailing problems with
> ClusterSSH and Leopard.

Hi Neil and others-
   I'm sorry I didn't see your message earlier because I've been  
chasing the same bug for a while. Neither of us mentioned ClusterSSH  
in our subject messages so we missed each other. My message was this:

    http://lists.macosforge.org/pipermail/macports-users/2008-January/008107.html

The problem with the cssh port as it exists is that the p5-tk port  
(currently without a maintainer) doesn't work. A simple script like  
this:

    use Tk;

causes a bus error.

I don't have the expertise to figure out why that is happening (and  
I've tried a bunch of things including back-revving to the 8.4.16 port  
of Tk) and haven't heard back from anyone who does. I tried asking the  
current Tk port maintainer (the very busy Markus) if he had any ideas  
but did not hear back. As a last resort, I just wrote the current Perl/
Tk maintainer last night but I haven't heard back from him either.

Your recipe gets around this problem by building Perl/Tk using the  
version of Tk that ships with Leopard. I'm trying to avoid that if I  
can because it means you are dropping your own user installed stuff  
into the Apple provided Perl tree vs. installing it into the MacPorts  
Perl installation. I did something like this for Tiger but was hoping  
to avoid sullying the Apple stuff this time around. I'd really prefer  
to get a working p5-tk port if possible.

As an aside, you asked about strace in your message. With the addition  
of Dtrace in Leopard (yay, Apple!), you can now get the same  
functionality. The easiest way to get this out of the box is to use  
the dtruss Dtrace script that ships with Leopard (just say "dtruss  
command", perhaps running under sudo).

        -- dNb


_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo/macports-users

[djinnii]

In this procedure, since Tk is installed into the Mac perl system by using "sudo /usr/bin/perl", when executing cssh it should also use the Mac perl system.

For some reason compiling cssh ends up using /opt/local/bin/perl instead.  Simply changing the first line of /usr/local/bin/cssh to use /usr/bin/perl instead solves the "Bus Error" issue.