diff options
| author | Jeremy Kerr <jk@ozlabs.org> | 2016-05-05 10:17:26 +0800 |
|---|---|---|
| committer | Jeremy Kerr <jk@ozlabs.org> | 2016-05-05 15:08:23 +0800 |
| commit | 235ccfc123806b736a50cc90838e634737c3842d (patch) | |
| tree | ae4ae3708eaad48125745d7d2004bb0ffd70e8e7 | |
| parent | 98100205157cfc4258e4e84ab8d512721eb847fc (diff) | |
| download | openbmc-docs-235ccfc123806b736a50cc90838e634737c3842d.tar.gz openbmc-docs-235ccfc123806b736a50cc90838e634737c3842d.zip | |
console: Fix code formatting
We need four spaces, not two.
Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
| -rw-r--r-- | console.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -14,7 +14,7 @@ Remote console connections To connect to an OpenBMC console session remotely, just ssh to your BMC on port 2200. Use the same login credentials you would for a normal ssh session: - $ ssh -p 2200 [user]@[bmc-hostname] + $ ssh -p 2200 [user]@[bmc-hostname] Local console connections @@ -23,11 +23,11 @@ Local console connections If you're already logged into an OpenBMC machine, you can start a console session directly, using: - $ obmc-console-client + $ obmc-console-client To exit from a console, type: - return ~ . + return ~ . Note that if you're on an ssh connection, you'll need to 'escape' the ~ character, by entering it twice. @@ -37,7 +37,7 @@ Logging Console logs are kept in: - /var/log/obmc-console.log + /var/log/obmc-console.log This log is limited in size, and will wrap after hitting that limit (currently set at 16kB). |
