'tahoe run' should not redirect stdout/stderr #1489

New Issue

tahoe-lafs · 2011-08-18T01:26:44Z

davidsarah commented

2011-08-18 01:26:44 +00:00

: 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 :)

: (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.

<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.

tahoe-lafs added the

labels 2011-08-18 01:26:44 +00:00

tahoe-lafs added this to the undecided milestone 2011-08-18 01:26:44 +00:00

tahoe-lafs added

minor

and removed

major

labels 2011-08-18 01:29:26 +00:00

davidsarah commented

2011-08-24 02:01:15 +00:00

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).

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).