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.
S
On Mon, 4 Jul 2005, Amir Binyamini wrote:
> Hello,
>
> >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.
and
: Oleg Goldshmidt <[EMAIL PROTECTED]>
Reply-To: linux-il@linux.org.il
To: "Amir Binyamini" <[EMAIL PROTECTED]>
CC: linux-il@linux.org.il
Subject: Re: "pidof" on a process (which was ran by passing arguments from
the command li
Date: 04 Jul 2005 11:40:59 +
"Amir
"Amir Binyamini" <[EMAIL PROTECTED]> writes:
> No.
> "pidof -x xend" returns an empty string.
Oh, that's because of env... If you had #!/usr/bin/python directly it
should have worked. One level of indirection too many...
Modify xend or try this:
pname () { /bin/ps auxww | /bin/egrep "$@" | /bin
No.
"pidof -x xend" returns an empty string.
Amir
From: Oleg Goldshmidt <[EMAIL PROTECTED]>
Reply-To: linux-il@linux.org.il
To: "Amir Binyamini" <[EMAIL PROTECTED]>
CC: linux-il@linux.org.il
Subject: Re: "pidof" on a process (which was ran by passing arguments from
the command line)
Date: 03
