On Tuesday 05 July 2005 03:53, guy keren wrote: > > >Oh, that's because of env... If you had #!/usr/bin/python directly... > > > changing to #!/usr/bin/python and running"pidof -x xend" did the work. > > > > The "env" is in he original Xend script but there is no problem for me to > > remove it.
Sure. While the 'env' hack is a nice trick in a private script, it is wrong when a system-wide program depends on the current path during it's running. > and loosing portability to platforms where python is installed in a > different path... This should be solved by the installation procedure on said platform which should substitute the correct path during "build" or "install" phase. If it was a C program I would call autoconf, but in python I think (haven't checked -- not a pythoneer) that 'setup.py' should have the equivalent mechanism. -- Oron Peled Voice/Fax: +972-4-8228492 [EMAIL PROTECTED] http://www.actcom.co.il/~oron ICQ UIN: 16527398 "The wonderful thing about standards is that there are so many of them to choose from." -- Grace Murray Hopper ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
