Re: [gentoo-dev] python-wrapper breaks init scripts

2009-10-05 Thread Michael Haubenwallner

Arfrever Frehtes Taifersar Arahesis wrote:
 2009-10-04 20:32:17 Hanno Böck napisał(a):
 I just stepped over a problem with the new python-wrapper. If I interpreted 
 the changelogs correctly, since eselect-python-20090801 /usr/bin/python is 
 no 
 longer a symlink, but a wrapper.
 
 Since eselect-python-20090804 /usr/bin/python is a symlink to a wrapper.
  
 I find this a questionable idea simply for the overhead it causes, but it 
 seems that this breaks all init-scripts using start-stop-daemon for python 
 scripts.

 Example:
 http://bugs.gentoo.org/show_bug.cgi?id=286191

 (same issue happens with some self-written python daemons we're using on our 
 servers)

 I don't know what the reasons were for the change from symlinks to a wrapper
 
 Ebuilds (usually through python.eclass) need to be able to set requested 
 version
 of Python without changing /usr/bin/python symlink. This is performed by 
 setting
 EPYTHON environment variable (E in the name of this variable is related to 
 words
 ebuild and eclass). If this variable isn't set, then Python wrapper uses
 version of Python configured using `eselect python`. Otherwise it uses 
 version of
 Python referenced by this variable.

The problem here IMO is that this wrapper executes python2.6 with argv0 set
to python2.6, while it should be the argv0 from how the wrapper was executed.
At least this is what init.d scripts expect (seen with ntlmaps too).

/haubi/



[gentoo-dev] python-wrapper breaks init scripts

2009-10-04 Thread Hanno Böck
Hi,

I just stepped over a problem with the new python-wrapper. If I interpreted 
the changelogs correctly, since eselect-python-20090801 /usr/bin/python is no 
longer a symlink, but a wrapper.

I find this a questionable idea simply for the overhead it causes, but it 
seems that this breaks all init-scripts using start-stop-daemon for python 
scripts.

Example:
http://bugs.gentoo.org/show_bug.cgi?id=286191

(same issue happens with some self-written python daemons we're using on our 
servers)

I don't know what the reasons were for the change from symlinks to a wrapper, 
but if it should stay the way it is, we need a fix for those issues.

-- 
Hanno Böck  Blog:   http://www.hboeck.de/
GPG: 3DBD3B20   Jabber/Mail:ha...@hboeck.de


signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-dev] python-wrapper breaks init scripts

2009-10-04 Thread Arfrever Frehtes Taifersar Arahesis
2009-10-04 20:32:17 Hanno Böck napisał(a):
 I just stepped over a problem with the new python-wrapper. If I interpreted 
 the changelogs correctly, since eselect-python-20090801 /usr/bin/python is no 
 longer a symlink, but a wrapper.

Since eselect-python-20090804 /usr/bin/python is a symlink to a wrapper.
 
 I find this a questionable idea simply for the overhead it causes, but it 
 seems that this breaks all init-scripts using start-stop-daemon for python 
 scripts.
 
 Example:
 http://bugs.gentoo.org/show_bug.cgi?id=286191
 
 (same issue happens with some self-written python daemons we're using on our 
 servers)
 
 I don't know what the reasons were for the change from symlinks to a wrapper

Ebuilds (usually through python.eclass) need to be able to set requested version
of Python without changing /usr/bin/python symlink. This is performed by setting
EPYTHON environment variable (E in the name of this variable is related to 
words
ebuild and eclass). If this variable isn't set, then Python wrapper uses
version of Python configured using `eselect python`. Otherwise it uses version 
of
Python referenced by this variable.

-- 
Arfrever Frehtes Taifersar Arahesis


signature.asc
Description: This is a digitally signed message part.