| 1 |
Arfrever Frehtes Taifersar Arahesis wrote: |
| 2 |
> 2009-10-04 20:32:17 Hanno Böck napisał(a): |
| 3 |
>> I just stepped over a problem with the new python-wrapper. If I interpreted |
| 4 |
>> the changelogs correctly, since eselect-python-20090801 /usr/bin/python is no |
| 5 |
>> longer a symlink, but a wrapper. |
| 6 |
> |
| 7 |
> Since eselect-python-20090804 /usr/bin/python is a symlink to a wrapper. |
| 8 |
> |
| 9 |
>> I find this a questionable idea simply for the overhead it causes, but it |
| 10 |
>> seems that this breaks all init-scripts using start-stop-daemon for python |
| 11 |
>> scripts. |
| 12 |
>> |
| 13 |
>> Example: |
| 14 |
>> http://bugs.gentoo.org/show_bug.cgi?id=286191 |
| 15 |
>> |
| 16 |
>> (same issue happens with some self-written python daemons we're using on our |
| 17 |
>> servers) |
| 18 |
>> |
| 19 |
>> I don't know what the reasons were for the change from symlinks to a wrapper |
| 20 |
> |
| 21 |
> Ebuilds (usually through python.eclass) need to be able to set requested version |
| 22 |
> of Python without changing /usr/bin/python symlink. This is performed by setting |
| 23 |
> EPYTHON environment variable ("E" in the name of this variable is related to words |
| 24 |
> "ebuild" and "eclass"). If this variable isn't set, then Python wrapper uses |
| 25 |
> version of Python configured using `eselect python`. Otherwise it uses version of |
| 26 |
> Python referenced by this variable. |
| 27 |
|
| 28 |
The problem here IMO is that this wrapper executes python2.6 with argv0 set |
| 29 |
to python2.6, while it should be the argv0 from how the wrapper was executed. |
| 30 |
At least this is what init.d scripts expect (seen with ntlmaps too). |
| 31 |
|
| 32 |
/haubi/ |
Archives