--- Holger Krull ha scritto:
Holger Krull schrieb:
Holger Krull schrieb:
I was to fast on my last email. I tested it now:
You need (on windows):
set DISPLAY=127.0.0.1:0.0 c:\cygwin\bin\bash.exe
-l /home/krull/test.sh
(it is important that there is no space between
0.0 and )
As someone pointed out in another post the sequence ps |grep has a risk of
finding grep itself in the list. The command pgrep combines both and hasn't
that risk.
Thanks Holger. Now this works perfectly. It does open
up a Windows cmd window – which remains open until I
finish with my app –
On Mon, Oct 01, 2007 at 05:33:12PM +0100, Phil Betts wrote:
It's probably not the cause of your problem, but you should
never use ps | grep xxx to detect if a process is running.
This is because the grep process will (sometimes) detect
itself and give you a false positive, and your xterm will
[EMAIL PROTECTED] wrote on Tuesday, October 02, 2007 4:21 PM:
On Mon, Oct 01, 2007 at 05:33:12PM +0100, Phil Betts wrote:
It's probably not the cause of your problem, but you should
never use ps | grep xxx to detect if a process is running.
This is because the grep process will (sometimes)
--- Holger Krull ha scritto:
As someone pointed out in another post the sequence
ps |grep has a risk of finding grep itself in the
list. The command pgrep combines both and hasn't
that risk.
Thanks for this tip.
That can be avoided by dual nested start like:
C:\cygwin\bin\bash.exe -c
Hello,
I am new bee here.
I am using Cygwin/X from my windows XP box to connect to my
development linux system via SSH X-port-forwarding. When I remote
desktop to windows XP, all the X windows slow down heavily. How do I
fix this issue?
Thanks,
Jeeva
--
Unsubscribe info:
