queue-developers

[Werner G. K. <wer...@ya...>]

Sven Hartrumpf <Sven.Hartrumpf@FernUni-Hagen.de> writes:

> On 7 Aug 2002, Lou Estey <lo...@un...> wrote:
> > We run GNU queue in a very limited way, with jobs looking like:
> >
> > queue -i -w -h <DNSname> -- <job>

> ssh should suffice for things like that.

> You might have to use cd in the <job> part and you
> might need to setup ssh so that you can login with ssh without
> a password, e.g. by using SSH keys:
> http://freshmeat.net/projects/ssh-with-keys-howto/

> Greetings
> Sven

When GQ was first developed, of course, ssh did not exist. Later, ssh became
a commercial product, and then eventually OpenSSH was born.

I personally liked to use GQ on my cluster in place of rsh because the
interface was more convenient and GQ was faster than rsh.

Once ssh became popular, it was often suggested that OpenSSH code be merged
into GQ (or vice versa) so that GQ would be a substitute for SSH with SSH
security. Eventually tarrif rules on cryptography were repealed, so this
became an attractive possibility but I never got around to do this. It's not
clear, of course, whether with SSH security GQ would be as fast as it is
without security. Then again, machines have become much faster, so starting
jobs with SSH libs might not be noticable different from current GQ
protocols, and only those concerned with benchmark will note the difference.

It feels good to be a peyon on this list and let someone else (our new
maintainer!) worry about which way to take GQ.

I'm still waiting for the introductory speach. I'm expecting Mike to write
something like "Friends, Romans, GQers, lend me your ears! I have come to
bury the previous maintainer, not to praise him." :-) Well, maybe not quite.
But I can't wait to see what GQ will look like in a year or so under new
management.