Custom Query (894 matches)
Results (91 - 93 of 894)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #915 | desai | https://me.yahoo.com/a/2SlxL.p_rsQD.KxOt3q32tWWsQ--#39bec | fixed | lock file does not work with python >= 2.5 |
| Description |
The bcfg2 agent uses fatal_error, which raises a SystemExit? exception, to abort after finding a lock file. This code is wrapped in a general try...except block though. In older versions of python, SystemExit? was uncatchable, but that is no longer true. This means that the agent will continue to try to configure the system even if a lock file exists. For example: $ cat test.py try:
except:
print 'got here' try:
except Exception:
print 'got here' $ python -V Python 2.6.4 $ python test.py got here $ As you can see, in newer versions of Python SystemExit? does not inherit from Exception, so you can fix the problem by using "except Exception:" instead. |
|||
| #391 | desai | [email protected]… | wontfix | libxml2 source rpm |
| Description |
Just an FYI, I wasn't able to build RPMs from the libxml2 source RPM on SLES 9 until I added this line to the top of the spec:
Otherwise it would fail saying "Installed (but unpackaged) file(s) found". Apparently you can also set this system-wide in /usr/lib/rpm/macros. -Theron |
|||
| #81 | desai | leggett | fixed | init script broken in 0.8.2 final |
| Description |
The bcfg2-server init script is broken for RHEL in 0.8.2 final. It worked in 0.8.2pre10. [[email protected]:~]$ sudo /etc/init.d/bcfg2 restart Password: /etc/init.d/bcfg2: line 37: log_begin_msg: command not found /etc/init.d/bcfg2: line 38: log_progress_msg: command not found pidof: invalid options on command line! pidof: invalid options on command line! /etc/init.d/bcfg2: line 40: log_end_msg: command not found /etc/init.d/bcfg2: line 31: log_begin_msg: command not found /etc/init.d/bcfg2: line 32: log_progress_msg: command not found /etc/init.d/bcfg2: line 34: log_end_msg: command not found |
|||
