Difference between revisions of "Sudosh"
(Started article) |
m (Sudosh (command) moved to Sudosh) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
'''sudosh''' is a filter and can be used as a login shell. <tt>sudosh</tt> 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. <tt>sudosh</tt> takes advantage of pty devices in order to sit between the user's keyboard and a program, in this case a shell. | ||
| − | <tt>sudosh</tt> was designed specifically to be used in conjunction with [[ | + | <tt>sudosh</tt> was designed specifically to be used in conjunction with [[sudo]] or by itself as a login shell. <tt>sudosh</tt> allows the execution of a root or user shell with logging. Every command the user types within the root shell is logged as well as the output. |
This is different then <code>"sudo -s"</code> or <code>"sudo /bin/sh"</code> because when you use one of these or a similar method instead of <tt>sudosh</tt> to start a new shell then this new shell does not log commands typed in the new shell to [[syslog]], only the fact that a new shell started is logged. If this newly started shell supports commandline history then you can still find the commands called in the shell in a file such as <code>.sh_history</code> but if you use a shell such as [[C shell|csh]] that does not support command-line logging you are out of luck.<br> | This is different then <code>"sudo -s"</code> or <code>"sudo /bin/sh"</code> because when you use one of these or a similar method instead of <tt>sudosh</tt> to start a new shell then this new shell does not log commands typed in the new shell to [[syslog]], only the fact that a new shell started is logged. If this newly started shell supports commandline history then you can still find the commands called in the shell in a file such as <code>.sh_history</code> but if you use a shell such as [[C shell|csh]] that does not support command-line logging you are out of luck.<br> | ||
| Line 10: | Line 8: | ||
==See also== | ==See also== | ||
| − | * [[ | + | *[[sudo]] |
| − | * [[ | + | *[[su]] |
| − | + | ||
| − | + | ||
| − | + | ||
| − | == External links == | + | ==External links== |
| − | * [http://sourceforge.net/projects/sudosh sudosh at SourceForge] | + | *[http://sourceforge.net/projects/sudosh sudosh at SourceForge] |
| − | * [http://www.sudo.ws/ sudo homepage] | + | *[http://www.sudo.ws/ sudo homepage] |
| − | * [http://en.wikipedia.org/wiki/Sudosh Wikipedia article on '''sudosh'''] | + | *[http://en.wikipedia.org/wiki/Sudosh Wikipedia article on '''sudosh'''] |
[[Category:Linux Command Line Tools]] | [[Category:Linux Command Line Tools]] | ||
Latest revision as of 02:03, 26 April 2007
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 or user shell with logging. Every command the user types within the root shell is logged as well as the output.
This is different then "sudo -s" or "sudo /bin/sh" because when you use one of these or a similar method instead of sudosh to start a new shell then this new shell does not log commands typed in the new shell to syslog, only the fact that a new shell started is logged. If this newly started shell supports commandline history then you can still find the commands called in the shell in a file such as .sh_history but if you use a shell such as csh that does not support command-line logging you are 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.)
