Be the first to post a text review of consh. Rate and review a project by clicking thumbs up or thumbs down in the right column.

• Release 0.01b is OUT

  Today, I finished 0.01b. It's very much like 0.01a, but a LOT more usable. I re-did the run-time environment directory structure to allow multiple conshd instances to be running on the same machine, I improved conshtool to the point where you can (and should) use it to start and stop conshd, and *drumroll* we have environment variables!

  posted by judecn 227 days ago

• File released: /consh/0.01b/consh-0.01b.tar.gz

  posted 227 days ago

• consh 0.01b file released: consh-0.01b.tar.gz

  (*) Greatly improved the daemon's runtime environment, so you can easily have multiple conshd instances running on the same physical machine. (*) The port on which a user connects to in order to communicate with conshd via the consh binaries is now stored in said runtime environment. (*) Your /tmp directory won't nearly be as cluttered, since worker sockets, etc. now live under /tmp/consh/$LOGNAME/ (*) The conshtool program works as expected. (*) You no longer need a consh_directory file; you instead have a system-wide /etc/conshd.hosts file and you let conshtool generate the directory for you. (*) Added cogetenv, cosetenv, and counsetenv commands for conshd environment variables (separate from bash environment variables, but for good reason--see the documentation).

  posted 228 days ago

• Yay! You cared enough to look here. So what *is* consh?

  Consh started out as a final project for a class in parallel and distributed computing I just finished. I'm continuing to work on it as a utility for shell junkies like myself who have multi-core CPUs (who doesn't these days?) and want an easy way to actually *use* them with as little tediousness as possible. Consh is one such solution--it provides a network overlay that abstracts the CPUs of hosts on a trusted LAN into a collection of uniquely-identifiable command executors (a.k.a. "workers") to which consh commands may assign work, with which consh commands may synchronize, and from which consh commands may receive shell command output from said work. In short, it creates a virtual multicomputer out of one or more computers, and lets the user tell the virtual CPUs (the workers) to run commands for them and give them back the output. So far, consh provides a way to run a given list of commands on one or more workers (the "co" command), a way to distribute iterations of a "for" loop across one or more workers (the "cofor" command), and a way to synchronize with one or more workers via a distributed barrier (the "cosync" command). In the near future, consh will also provide a distributed environment variable collection and a way for workers to send and receive data from one another (through environment variables). To allow for otherwise normal shell behavior, consh runs on top of a Bourne-compatible shell and simply delegates typical shell commands to it. The current stable release (i.e. the one I turned in for class) is the 0.01a release, but you'll find the best stuff in Subversion. I do NOT willingly commit code that doesn't work, so Subversion snapshots are "reasonably" stable in that I have tried it out and confirmed that it works and put it through valgrind to make sure there aren't any memory-related errors. You'll need libreadline and its development files to compile consh. Feel free to e-mail me with questions.

  posted by judecn 233 days ago

• File released: /consh/0.01a/consh-0.01a.tar.gz

  posted 234 days ago

• consh 0.01a file released: consh-0.01a.tar.gz

  posted 235 days ago