mirror of
https://github.com/xcat2/confluent.git
synced 2024-11-26 03:19:48 +00:00
6acaac8644
When a log object is used as a 'dumb' file target, show the origin of the
output. The motivation here is that 'print' statements are intended to
be an unusual event that should be easily tracked down and eliminated
once their specific use has concluded.
In xcatd, running '-f' means a lot of mysterious output that is hard
to manage as they frequently print out variable contents without
searchable context. For example, if in xcatd someone randomply prints out
a varibale with a nodename, we might see a stray:
n1
With this change (together with previous changes), the same statement
results in stdout log appearing like:
Jan 19 14:20:54 File "/opt/confluent/lib/python/confluent/plugins/hardwaremanagement/ipmi.py", line 364, in _dict_sensor
print nodename: n1
|
||
|---|---|---|
| .. | ||
| bin | ||
| confluent | ||
| sysvinit | ||
| buildrpm | ||
| confluent_server.spec.tmpl | ||
| makesetup | ||
| MANIFEST.in | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py.tmpl | ||
| VERSION | ||