- 29 Dec, 2000 3 commits
-
-
Christopher Alfeld authored
-
David G Andersen authored
-
mac authored
-
- 28 Dec, 2000 8 commits
-
-
Mike Hibler authored
mode so no one can open it between the time capture does the revocation and we change the group/mode to the new user.
-
mac authored
-
mac authored
-
Leigh B. Stoller authored
-
Christopher Alfeld authored
-
Leigh B. Stoller authored
script runs out of nalloc and nfree and figures out what project (group) a node is in. It does an ssh over to plastic to run the other script that does the actual work.
-
Leigh B. Stoller authored
-
Leigh B. Stoller authored
-
- 27 Dec, 2000 6 commits
-
-
mac authored
-
mac authored
-
Christopher Alfeld authored
seperated node in the /os/nodes table.
-
Christopher Alfeld authored
-
mac authored
-
mac authored
-
- 26 Dec, 2000 10 commits
-
-
Mike Hibler authored
Taken from the man page (ntip.1): ---- Ntip differs from the traditional tip in a number of ways: 1. It does not support calling a remote system, all auto-dialing code has been removed. 2. All the cheezy file transfer support has been removed. 3. Most of the tilde escapes have been removed. Mostly these were the file trasfer related ones. See below for what remains. 4. Ntip ignores 90% of the remote(5) capabilities. You can set the baud rate (br) and the device (dv). Period. 5. All of tips variables are still present, but most don't do anything. It is left as an exercise to the interested user to differentiate. 6. By default, it operates in ``raw'' mode instead of the usual ``cbreak'' mode. This means that all input processing (if any) is performed by the remote system. Raw mode also disables ``raisechar'' and ``force'' variable interpretation. Yes, you can actually run emacs on an ntip line (modulo the '~' thing). 7. Tip is the poster-child for fork-without-exec, creating separate reader and writer processes executing ``the same code.'' Ntip is a child of convenience and consists of a single process using select(2). 8. Ntip no longer uses uucp(1) style locking. It relies on the TIOCEX- CL ioctl (see tty(4)) to provide ``reasonably mutually exclusive'' access. While it is still technically possible that two parties could open the same line and both get ``exclusive'' access to it, we consider this to be the source of amusing anecdotes rather than a bug. ----
-
Christopher Alfeld authored
-
Christopher Alfeld authored
-
Christopher Alfeld authored
-
Christopher Alfeld authored
-
Mike Hibler authored
-
Christopher Alfeld authored
direct_link scores that pop up.
-
Christopher Alfeld authored
-
Christopher Alfeld authored
files. Note: none of the backend has been written yet. Also did a number of minor bug fixes. The most serious bug showed up when you have a topology with no links.
-
Leigh B. Stoller authored
code I found in /foo/x/mike/src/capture/capture.c. Second, add a -r option to open up a second log file called the "run" file, which is intended to be used for the experiment session log. This log is restarted with a SIGUSR1. Third, add SIGUSR2 handler to close the pty side of the capture, which has the nice side effect of causing tip to exit gracefully.
-
- 22 Dec, 2000 9 commits
-
-
Christopher Alfeld authored
-
Christopher Alfeld authored
checking. Also made it so that .1 addresses were no longer assigned and it now works when run on IR files that already have a /ip section.
-
Mike Hibler authored
-
Leigh B. Stoller authored
some informative messages instead of just going away for 5 minutes.
-
Christopher Alfeld authored
-
Leigh B. Stoller authored
-
Leigh B. Stoller authored
-
Leigh B. Stoller authored
STDOUT so the web page has something to show for itself.
-
Leigh B. Stoller authored
rest to STDERR.
-
- 21 Dec, 2000 4 commits
-
-
mac authored
-
mac authored
-
Leigh B. Stoller authored
-
mac authored
-