- 30 May, 2014 1 commit
-
-
Mike Hibler authored
Needed when boss is the tip server (i.e., for IPMI consoles). Somehow this vaguely feels like a potential flaw. Prior to this, a misconfigured sshtb command that specified boss would fail. Now it will succeed and run in the one place it can cause the most damage. Also, fix a couple of nits in the console code.
-
- 24 Sep, 2012 1 commit
-
-
Eric Eide authored
This commit is intended to makes the license status of Emulab and ProtoGENI source files more clear. It replaces license symbols like "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited blocks that contain actual license statements. This change was driven by the fact that today, most people acquire and track Emulab and ProtoGENI sources via git. Before the Emulab source code was kept in git, the Flux Research Group at the University of Utah would roll distributions by making tar files. As part of that process, the Flux Group would replace the license symbols in the source files with actual license statements. When the Flux Group moved to git, people outside of the group started to see the source files with the "unexpanded" symbols. This meant that people acquired source files without actual license statements in them. All the relevant files had Utah *copyright* statements in them, but without the expanded *license* statements, the licensing status of the source files was unclear. This commit is intended to clear up that confusion. Most Utah-copyrighted files in the Emulab source tree are distributed under the terms of the Affero GNU General Public License, version 3 (AGPLv3). Most Utah-copyrighted files related to ProtoGENI are distributed under the terms of the GENI Public License, which is a BSD-like open-source license. Some Utah-copyrighted files in the Emulab source tree are distributed under the terms of the GNU Lesser General Public License, version 2.1 (LGPL).
-
- 21 Apr, 2012 1 commit
-
-
Leigh Stoller authored
node. There auth method has to be ssh-key in the DB, since I did not feel like dealing with password auth and the required tty stuff.
-
- 19 Jan, 2012 1 commit
-
-
Leigh Stoller authored
virtual nodes. We now create an interfaces table entry so that we do not special code to find the control network interface. This entry is delated along with the node entries when the experiment is swapped out. Of course, we still have existing nodes with jailip entries, so not much code was removed, but this saves me from having to add more special cases for XEN elabinelab, and at some point we can remove the deprecated code.
-
- 10 Aug, 2011 1 commit
-
-
Leigh Stoller authored
USERNODE, shortcut to exec only, without the ssh.
-
- 31 Jul, 2009 1 commit
-
-
David Johnson authored
-
- 15 Oct, 2008 1 commit
-
-
David Johnson authored
username out of the db. Don't want to try slogin as root from a script.
-
- 05 Dec, 2007 1 commit
-
-
Leigh Stoller authored
-
- 17 Aug, 2007 1 commit
-
-
Leigh Stoller authored
different then the original widearea code. Simpler, less dynamic. First off, the wanodecreate script creates a new widearea_nodeinfo entry. These are nodes that will later checkin and be created as a real node. The input is a little xml file that you can use to specify the stuff in the table entry (city, state, zip, etc). You can also provide a privkey (no more then 64 chars), or one will be generated for you. For each one of these, create a Dongle Boot and stash the privkey as /etc/emulab/emulab-privkey on the dongle. You do not assign the IP address; the node will tell us that when it checks in. A node checks in like this: https://$bossname/wanodecheckin.php?IP=$IP&privkey=$privkey &hostname=$hostname The web page is simply a stub that makes sure the arguments don't have any illegal characters, and then passes off to the backend. The backend script checks the privkey and finds the widearea_nodeinfo. The first time the node checks in, the node is created (db/Node.pm) (nodes table, interfaces table, etc), and the node is moved to hwdown. Subsequent checkins watch for changes to the IP or hostname, and issue named_setup calls as needed.
-
- 14 Dec, 2005 1 commit
-
-
Kirk Webb authored
Doh! sshtb needs to exit with the status of the child process when trying sshv2 and able to connect.
-
- 12 Dec, 2005 1 commit
-
-
Kirk Webb authored
Be default sshtb now tries to ssh to the specified node via protocol version 2. It will try protocol version 1 if a v2 connection/auth fails. This was a little messy to implement since sshtb now has to fork the first ssh attempt and wait to see if it succeeds (all the fun of dealing with signals and killing off the child ssh process and whatnot).
-
- 27 Jan, 2005 1 commit
-
-
Leigh Stoller authored
before the exec to avoid holding open the mysqld socket in the new process.
-
- 20 Aug, 2004 1 commit
-
-
Leigh Stoller authored
pass a string with embedded quotes, perl hands it off to a shell which results in an extra shell wrapper for every ssh. Well, with SSH_ARGS the way they are, that means we always get the extra shell. While this is a nice optimization it actually matters mostly from linktest_control where I want to make sure that the child that invokes linktest on ops (an ssh) can be killed directly with TERM (say, if user cancels linktest) without worrying about intervening shell screwing with signals, etc.
-
- 22 Mar, 2004 1 commit
-
-
Robert Ricci authored
way, we don't have to worry about sshtb getting killed but its child process hanging around.
-
- 22 Aug, 2003 1 commit
-
-
Austin Clements authored
that jails do. sshtb can now handle vnodeid's, and must be given a vnodeid if it's a Plab node, because the username will differ depending on this.
-
- 09 Jul, 2003 1 commit
-
-
Leigh Stoller authored
-
- 07 Jul, 2002 1 commit
-
-
Leigh Stoller authored
-
- 24 Jun, 2002 1 commit
-
-
Robert Ricci authored
links that do not need to get created in the ops install target. sshtb also checks for unified control nodes, and if the destination host is one of them, just runs the command, rather than invoking it remotely via ssh.
-
- 05 Jun, 2002 1 commit
-
-
Leigh Stoller authored
script that checks the database to see if local or remote. The problem with this is that the ssh syntax makes it hard to determine the host name by inspection. Would need to parse all the ssh args (bad idea), ot work backwards and try to figure out the difference between the command (which is not a string but a sequence of args) and the host and the preceeding ssh args. Hell with that! Changed sshtb to require a specific -host argument. Read the args and look for it. Error out of not found, to catch improper usage. The moral of this update: "sshtb [ssh args] -host <host> [more args ...]
-
- 12 Jul, 2001 1 commit
-
-
Leigh Stoller authored
node_reboot fail oddly cause the kill -TERM was killing the shell process but not the ssh!
-
- 26 Jun, 2001 1 commit
-
-
Robert Ricci authored
sshtb is a _very_ simple shell script that runs ssh with a few commandline parameters, which make it play nicer in an script environment. These parameters can be changed with the '--with-ssh-args' argument, but default to: '-q -o "BatchMode yes" -o "StrictHostKeyChecking no"' All ssh calls now use this script.
-