Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verbosity parameters #45

Open
zeelot opened this issue Aug 21, 2011 · 6 comments
Open

Verbosity parameters #45

zeelot opened this issue Aug 21, 2011 · 6 comments
Labels

Comments

@zeelot
Copy link
Member

zeelot commented Aug 21, 2011

There should be a standard way to add -v one or more times to increase how much output is generated. We might also want a -q for the opposite effect.

This is related to #39 and some discussion has already happened there but I am splitting that ticket up :)

@samsoir
Copy link

samsoir commented Oct 7, 2011

Definitely would be nice to have a fully verbose mode that outputs the current state of minion to STDERR. E.g.

Executing task:
[ DONE ]

etc etc

(should this be a separate feature request?)

@samsoir
Copy link

samsoir commented Oct 7, 2011

So, STDOUT is agreed as the better target for this messaging

@BRMatt
Copy link
Member

BRMatt commented Oct 10, 2011

Any reasons why? Haven't checked the logs yet and it'd be good to know the reasoning for future reference

@samsoir
Copy link

samsoir commented Oct 10, 2011

Some minion tasks can appear to either be doing nothing or stalled as they can take over 10 minutes to produce any output. This especially happens when a number of migrations are executed together. It would be a better user experience to be able to optionally generate status output during each tasks execution.

@BRMatt
Copy link
Member

BRMatt commented Oct 10, 2011

Sorry, I meant why STDOUT VS. STDERR

@samsoir
Copy link

samsoir commented Oct 10, 2011

You could argue that verbose output to the client is not strictly an error condition. I would accept that argument. My initial suggestion was purely based on my C programming where I debug output to STDERR. STDOUT would be better, as it is easier to pipe elsewhere (if that was required or appropriate - I doubt it to be honest).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants