Author: Matt Kennedy
Jumppoint is an administration tool to ease the lives of people who must maintain many remote systems. At its simplest, it's a little utility to maintain your login settings for all your remote hosts and launch SSH sessions automagically. At its most complex, jumppoint has it's own builtin Perl scripting engine that allows you to write scripts to automate common tasks and perform them on multiple hosts.
Jumppoint currently is capable of the following:
To run jumppoint using the precompiled RPM package, you will need the following packages installed:
If you plan on compiling from source, you will need the following in addition to the previous items:
Most of these packages are standard on most linux distributions. The hard to find stuff is available from this site.
When run for the first time jumppoint will create a directory called .jumppoint in your home directory. This is where are the configuration files and custom extensions go. Examples of the configuration files are available in the download directory. I will document this stuff thoroughly as soon as I get time
There ain't much at the moment. For now, here is the documentation available:
Source and Binary RPMs for the latest version of jumppoint are now available for Red Hat, the binary RPM will not play nice with the latest Mandrake. Debian packages coming Real Soon Now. For instructions on downloading and installing jumppoint, plus a list of what you need on your system, please see the README file.
The source tarball includes the headers and precompiled libraries for the development version of the FLTK GUI toolkit. If you need to build FLTK from source you'll need to fetch a cvs snapshot of FLTK. The snapshot that this version of jumppoint is built against is in the download directory.
How is jumppoint licensed?
Jumppoint is available under the GNU General Public License. It was written for the benefit of the tech guys where I work at Jumpline.com, but the owners are real cool and let me GPL it.
What does it run on?
Jumppoint runs on Linux, and may work on other *nixes, but I haven't tried it yet.
Is there a Windows version?
No. Due to the extreme pain in the butt that Windows porting involves a Win32 port will occur only if one of 3 conditions are met:
Why does jumppoint hang on my system when trying to connect to a
Check your version of Expect. Some versions of Expect 5.31 have a bug in which it hangs when spawning a new process on some systems (notably Debian). To fix it you must link against a working version of libexpect (expect 5.28 works fine, so RedHat and Mandrake people should be cool). If Expect is fine on your system, you may run into problems if you have configured SSH to not do password authentication, jumppoint expects a password prompt from SSH and will wait for it.
How come my XTerm keeps dying when I try to connect from the
If you are using gnome-terminal that program has issues with shared memory extensions through gdk. I've had it barf on me frequently if more than 8 terminals are open and have seen it die with fewer on other machines. If this happens to you, try another XTerm.
Does it work with Perl 5.6.0?
Sort of. I does get problematic when built against or using modules for 5.6.0. I haven't tracked this down yet. I've found no problems with 5.005_x version of Perl.
I'm having problems compiling with gcc 2.95.2...
Earlier versions of jumppoint worked with 2.95.2, but I haven't updated the new code yet. Util I do you can build jumppoint by running the configure script with the --enable-gcchack option. Also, SWIG and gcc 2.95.2 don't play nice together. To build SWIG with 2.95.2 add the -fpermissive flag to the CFLAGS and CXXFLAGS variables of the makefiles in SWIG.
How do I make some cool jumppoint scripts?
Jumppoint uses Perl for its scripting engine. Both the binary and source packages of jumppoint contain documentation of the functions unique to it. The scripts/ directory of jumppoint also contains several examples (some even useful) to get you started.
Last Modified On: July 20, 2000