Skip to content

Commit 37275e3

Browse files
authored
updating logs for consistency with scripts
BlockchainCommons/Bitcoin-Standup-Scripts#23
1 parent 4b3dc0d commit 37275e3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

02_1_Setting_Up_a_Bitcoin-Core_VPS_with_StackScript.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,7 @@ Here's a little catch: _your StackScript is running right now_. The BASH script
122122

123123
The total run time is about 10 minutes. So, go take a break, get an espresso, or otherwise relax for a few minutes. There are two parts of the script that take a while: the updating of all the Debian packages; and the downloading of the Bitcoin code. They shouldn't take more than 5 minutes each, which means if you come back in 10 minutes, you'll probably be ready to go.
124124

125-
If you're impatient you can jump ahead and `sudo tail -f ~root/standup.log` which will display the current progress of installation, as described in the next section.
125+
If you're impatient you can jump ahead and `sudo tail -f /standup.log` which will display the current progress of installation, as described in the next section.
126126

127127
## Verify Your Installation
128128

@@ -150,7 +150,7 @@ $ rm *
150150
In order to ensure that the downloaded Bitcoin release is valid, the StackScript checks both the signature and the SHA checksum. You should verify that both of those tests came back right:
151151

152152
```
153-
$ sudo grep VERIFICATION ~root/standup.log
153+
$ sudo grep VERIFICATION /standup.log
154154
```
155155

156156
If you see something like the following, all should be well:
@@ -167,13 +167,13 @@ You may also want to read through all of the setup log files, to make sure that
167167

168168
It's best to look through the standard StackScript log file, which has all of the output, including errors:
169169

170-
`$ sudo more ~root/standup.log`
170+
`$ sudo more /standup.log`
171171

172172
Note that it is totally normal to see _some_ errors, particularly when running the very noisy gpg software and when various things try to access the non-existant `/dev/tty` device.
173173

174174
If you want instead to look at a smaller set of info, all of the errors should be in:
175175

176-
`$ sudo more ~root/standup.err`
176+
`$ sudo more /standup.err`
177177

178178
It still has a fair amount of information that isn't errors, but it's a quicker read.
179179

0 commit comments

Comments
 (0)