juju-log vs. command line length limits
Bug #1274460 reported by
Stuart Bishop
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
juju-core |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
juju-log currently requires the log message to be passed on the command line. This means that hooks can unexpectedly fail if they manage to exceed the maximum command line length.
This problem could be worked around if juju-log was able to read in the log message from stdin. This would also be useful in other situations too:
./long-running-task 2> >(juju-log -l ERROR --pipe 1>&2) > >(juju-log -l DEBUG --pipe)
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
tags: | added: juju-log |
Changed in juju-core: | |
importance: | High → Medium |
tags: | added: canonical-is |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.1.0 |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
milestone: | 2.1-rc2 → none |
To post a comment you must log in.
Not only that, if you have something like this:
"""
output=$(some command)
# output has "-e: option unknown"
juju-log "$output"
"""
juju-log won't log the output, but an error of its own (since it doesn't know the -e option).