Skip to content
This repository was archived by the owner on Apr 24, 2022. It is now read-only.

Message logging #79

Closed
eLvErDe opened this issue Jun 28, 2017 · 6 comments
Closed

Message logging #79

eLvErDe opened this issue Jun 28, 2017 · 6 comments

Comments

@eLvErDe
Copy link

eLvErDe commented Jun 28, 2017

Hi,

I just started ethminer in a Mesos cluster and the output is kinda inappropriate for this.
I see two issues here:

  • Most of the logs goes to stderr instead of stdout
  • It uses colorized output that Mesos cannot handle (may I ask for a command line switch disabling this ? ;)

Regards, Adam.

@chfast
Copy link
Contributor

chfast commented Jul 3, 2017

The ethminer does not check at runtime if there is a terminal color support. See https://github.com/ethereum-mining/ethminer/blob/master/libdevcore/Terminal.h.

@ghost
Copy link

ghost commented Jul 6, 2017

wait, what? The miner has color support?
If yes: Colors are not supported on Windows yet, right?

@chfast
Copy link
Contributor

chfast commented Jul 6, 2017

No colors on Windows, right. Blame Windows.

@jimmykl
Copy link
Contributor

jimmykl commented Jul 6, 2017

Yep @chfast it's Windows fault. I did some research and it's a known issue after the anniversary update. There is way to enable 'legacy' console support during compile I just need to get my head around configuring it.

@chfast
Copy link
Contributor

chfast commented Jul 6, 2017

If would forget about legacy cmd. I think PowerShell supports colors, so someone can add support for it.

@ghost
Copy link

ghost commented Jul 6, 2017

I don't think it would be false to support the 'legacy' terminal/console on Windows because 99% of the users out there will use it. But that's a discussion for itself...

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

No branches or pull requests

4 participants