aboutsummaryrefslogtreecommitdiff
path: root/system/sudosh2/README
diff options
context:
space:
mode:
authorB. Watson <yalhcru@gmail.com>2022-03-14 12:53:31 -0400
committerB. Watson <yalhcru@gmail.com>2022-03-17 12:38:12 -0400
commit36d87be55709f5cd2500a3a6f9895eb9a5466182 (patch)
tree843dea36938f403d9a4d9480feb86e631e0302f9 /system/sudosh2/README
parentcb375e0a102b321b8b90469a22388bc22196ce63 (diff)
system/sudosh2: Wrap README at 72 columns.
Signed-off-by: B. Watson <yalhcru@gmail.com>
Diffstat (limited to 'system/sudosh2/README')
-rw-r--r--system/sudosh2/README20
1 files changed, 10 insertions, 10 deletions
diff --git a/system/sudosh2/README b/system/sudosh2/README
index cb5fa47a868e4..6a68645ba9385 100644
--- a/system/sudosh2/README
+++ b/system/sudosh2/README
@@ -1,18 +1,18 @@
-sudosh is a filter and can be used as a login shell. sudosh takes advantage
-of pty devices in order to sit between the user's keyboard and a program, in
-this case a shell.
+sudosh is a filter and can be used as a login shell. sudosh takes
+advantage of pty devices in order to sit between the user's keyboard
+and a program, in this case a shell.
-sudosh was designed specifically to be used in conjunction with sudo or by
-itself as a login shell.. sudosh allows the execution of a root shell with
-logging. Every command the user types within the root shell is logged as
-well as the output.
+sudosh was designed specifically to be used in conjunction with sudo
+or by itself as a login shell.. sudosh allows the execution of a
+root shell with logging. Every command the user types within the root
+shell is logged as well as the output.
How is this different than "sudo -s" or "sudo /bin/sh" ?
Using "sudo -s" or other methods doesn't log commands typed to syslog.
-Generally the commands are logged to a file such as .sh_history and if you
-use a shell such as csh that doesn't support command-line logging you're
-out of luck.
+Generally the commands are logged to a file such as .sh_history and if
+you use a shell such as csh that doesn't support command-line logging
+you're out of luck.
sudosh fills this gap. No matter what shell you use, all of the command
lines are logged to syslog (including vi keystrokes.)