Johannes,
Could you ensure in /usr/share/pgsql/postgresql.conf that bytea_output =
'escape', and if not see if that corrects your problem?
-Stephen
On 08/14/2012 08:57 AM, Stephen Herr wrote:
Hi Johannes,
Can you please give me more information on the system where you are
experiencing this problem?
We had a bug with identical symptoms where the root cause was that the
defaults on how a particular object was stored (as ascii or as hex) in
Postgresql changed in newer versions of the database. If that is the
root cause of your problem, then it would not be safe to simply assume
that we will always get hex back and expand it out to ascii, because
that would generate errors for people who are running older versions
of Postgresql. My cursory search has not turned up the original bug,
but I will keep looking.
-Stephen
On 08/14/2012 06:18 AM, Johannes Renner wrote:
Hello,
we found out that script contents are not properly displayed in the
web UI
in "Systems" -> "Events" -> "History" (it's a perl page ...).
To reproduce:
- choose a system and go to "Remote Command"
- type in some script contents, e.g. "a b c d e f g h"
- schedule the command
- go to "Events" and click on the one just scheduled
- in the "Details" you will see (for the example above):
x23212f62696e2f73680a0a61206220632064206520662020672068
which is the ASCII code for
"
#!/bin/sh
a b c d e f g h
"
The attached patch fixes the problem by converting the ASCII codes into
a string using the pack() function.
Regards,
Johannes
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
