Bitcoin Forum
May 08, 2024, 11:05:38 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Reaper Log File  (Read 1450 times)
kevindeangelis (OP)
Full Member
***
Offline Offline

Activity: 448
Merit: 130


3D-Printing goes Blockchain!


View Profile
June 06, 2013, 09:43:41 PM
 #1

I'm using Ubuntu 13.04, Anyone know how to get reaper to log the output and run in the background? 
I've tried "./reaper & > mylog.log" but no luck. I just end up with an empty file.

Thanks in advance.

There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715166338
Hero Member
*
Offline Offline

Posts: 1715166338

View Profile Personal Message (Offline)

Ignore
1715166338
Reply with quote  #2

1715166338
Report to moderator
1715166338
Hero Member
*
Offline Offline

Posts: 1715166338

View Profile Personal Message (Offline)

Ignore
1715166338
Reply with quote  #2

1715166338
Report to moderator
TheSpiral
Full Member
***
Offline Offline

Activity: 322
Merit: 113


Sinbad Mixer: Mix Your BTC Quickly


View Profile
June 06, 2013, 09:59:10 PM
 #2

Not on my linux box at the moment, but try adding 2>&1 to the end.
./reaper & > mylog.log 2>&1
kevindeangelis (OP)
Full Member
***
Offline Offline

Activity: 448
Merit: 130


3D-Printing goes Blockchain!


View Profile
June 06, 2013, 10:07:02 PM
 #3

Not on my linux box at the moment, but try adding 2>&1 to the end.
./reaper & > mylog.log 2>&1

hmmm... thanks for the reply, but I gave that a try and I'm still getting the same results.

TheSpiral
Full Member
***
Offline Offline

Activity: 322
Merit: 113


Sinbad Mixer: Mix Your BTC Quickly


View Profile
June 06, 2013, 10:43:13 PM
 #4

Not on my linux box at the moment, but try adding 2>&1 to the end.
./reaper & > mylog.log 2>&1

hmmm... thanks for the reply, but I gave that a try and I'm still getting the same results.
Woops. K, had to run downstairs and check on my headless box.
It's:
./reaper | tee my.log

At least, it works with my cgminer script, assuming it does the same with Reaper.
kevindeangelis (OP)
Full Member
***
Offline Offline

Activity: 448
Merit: 130


3D-Printing goes Blockchain!


View Profile
June 06, 2013, 10:50:18 PM
 #5

Not on my linux box at the moment, but try adding 2>&1 to the end.
./reaper & > mylog.log 2>&1

hmmm... thanks for the reply, but I gave that a try and I'm still getting the same results.
Woops. K, had to run downstairs and check on my headless box.
It's:
./reaper | tee my.log

At least, it works with my cgminer script, assuming it does the same with Reaper.

That worked! .. well, with a "&" at the end

ie: ./reaper | tee my.log &


Thanks!

BenTuras
Hero Member
*****
Offline Offline

Activity: 826
Merit: 1001



View Profile
June 07, 2013, 08:43:37 AM
 #6

Better is ./reaper 2>&1 | tee -a my.log &

You'll then also catch all error messages(2>&1) in your logfile and append(-a) it to your logfile if the logfile already exist. This way you will not overwrite your logfile if you start reaper again.

Without 2>&1, you'll only log all standard output messages in your logfile.

BTW, the error in your first command line was that you were starting reaper in the background(./reaper & ) and an empty command(> mylog.log) that was sending its output to your logfile, hence your logfile was empty.

I am selling in stock OneStringMiner boards, based on the Bitfury chips. Have a look here: https://bitcointalk.org/index.php?topic=495536.0
kevindeangelis (OP)
Full Member
***
Offline Offline

Activity: 448
Merit: 130


3D-Printing goes Blockchain!


View Profile
June 07, 2013, 08:54:52 AM
 #7

BTW, the error in your first command line was that you were starting reaper in the background(./reaper & ) and an empty command(> mylog.log) that was sending its output to your logfile, hence your logfile was empty.

DOH! you're right! .. Thanks!

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!