Opened at 2011-08-18T01:26:44Z

Closed at 2014-12-06T23:00:09Z

#1489 closed defect (fixed)

'tahoe run' should not redirect stdout/stderr

Reported by: davidsarah Owned by: Lcstyle
Priority: normal Milestone: 1.10.1
Component: code Version: 1.8.2
Keywords: logging easy Cc:
Launchpad Bug:

Description (last modified by Lcstyle)

<warner>: so first off, any 'print's in the gateway will show up in NODEDIR/logs/tahoesvc.log twistd.log, not on stdout

<T_X>: ah! okay, I was already wondering whether something gets redirected :)

<warner>: (that's always true when launched with 'tahoe start', but I think it may also currently be true when run with 'tahoe run', although I'd love to fix that)

This would be very useful for debugging.

Change History (11)

comment:1 Changed at 2011-08-18T01:29:26Z by davidsarah

  • Description modified (diff)
  • Priority changed from major to minor

comment:2 Changed at 2011-08-18T04:32:04Z by zooko

  • Description modified (diff)

comment:3 Changed at 2011-08-18T04:38:35Z by davidsarah

  • Description modified (diff)

comment:4 Changed at 2011-08-18T04:38:48Z by davidsarah

  • Description modified (diff)

comment:5 Changed at 2011-08-24T02:01:15Z by davidsarah

  • Milestone changed from undecided to eventually
  • Priority changed from minor to major

This would also allow you to use "import pdb; pdb.set_trace()" to trap into the Python debugger from a node run using tahoe run. Currently that's unusable because of the redirection to tahoesvc.log (but I don't think there is any other obstacle to doing it).

comment:6 Changed at 2012-04-01T04:44:53Z by davidsarah

  • Keywords easy added
  • Milestone changed from eventually to 1.10.0
  • Owner changed from somebody to davidsarah
  • Status changed from new to assigned

comment:7 Changed at 2012-09-04T16:46:28Z by warner

  • Milestone changed from 1.10.0 to 1.11.0

good idea, but no code yet, so pushing out to next release

comment:8 Changed at 2014-09-27T02:27:39Z by Lcstyle

  • Description modified (diff)
  • Owner changed from davidsarah to Lcstyle
  • Status changed from assigned to new

debugging is what I do, sounds like an easy fix.

comment:9 Changed at 2014-09-27T02:29:05Z by Lcstyle

  • Status changed from new to assigned

comment:10 Changed at 2014-09-27T13:41:38Z by daira

  • Milestone changed from soon to 1.12.0
  • Priority changed from major to normal

comment:11 Changed at 2014-12-06T23:00:09Z by daira

  • Milestone changed from 1.12.0 to 1.11.0
  • Resolution set to fixed
  • Status changed from assigned to closed

This was fixed in [87a6894e6299148d639279fbd909110ba00d0080/trunk].

Note: See TracTickets for help on using tickets.