1) double clicking xterm.exe results in two windows - a command window plus the xterm - this is unacceptable 2) I have used putty a lot in the past; I simply prefer xterm which I have been using since the beginning of X-Windows 3) I have used cron for backup in the past and use it on various Linux VMs for various purposes; with this new(er) computer I wanted to avoid having another background service running when Windows theoretically offers a good solution. In any case, it worked for over a year.
On Wed, Mar 12, 2014 at 4:19 PM, Andrey Repin <anrdae...@yandex.ru> wrote: > Greetings, Gulliver Smith! > >> My system is Windows 7 professional 64 bit. The Cygwin is 32 bit, >> updated monthly > >> I have a backup script that used to run successfully from a Windows >> shortcut or scheduled task as > >> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c >> "/home/gulliver/bin/backup >> /cygdrive/c/temp/backup.log 2>&1" > >> However, around August 2013 this stopped working (it took me a while to >> notice) > > run is known to crash at random occasions, since... around that time. > I don't know if it has been fixed, sorry. > That aside, I see no reason to use run in your case. > >> If I try in a windows command prompt it also crashed, > >> I get a small run.exe.stackdump file: > >> Stack trace: >> Frame Function Args >> 00284B28 610303D2 (00000114, 0000EA60, 000000A4, 00284B78) >> 00284C38 610DA4DD (00000000, 00650000, 00284C78, 0028CE64) > >> The problem is not with the bash command or script - it runs fine from >> both the command prompt or a shortcut if I change the command to > >> C:\cygwin\bin\bash.exe -l -c "/home/gulliver/bin/backup >> >> /cygdrive/c/temp/backup.log 2>&1" > >> but then there is an empty Windows window open for the whole time. > > Use cron, then there won't be any stray windows. > >> A related issue is an xterm shortcut that used to work: > >> C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "xterm.exe -title TTTTT >> -bg '#EEFFFE' -e ssh -Y xxxx@yyyy&" > > Now, THIS is a VERY wrong way to do it. > You're > 1. Starting run > 2. Telling it to start bash > 3. Telling bash to start xterm > 4. In which you're starting an SSH session. > > Why not start xterm directly? Also, ever heard of PuTTY? Or mintty? > >> This used to work as intended. Now it opens an xterm on the local host >> only - the ssh command fails. Again, removing the "run" and executing >> "bash" directly works but opens a second window. > >> Does anyone know what might be happening or how to debug this problem? > > Most simple solution would be to use right tools for the job, I'd say. > > > -- > WBR, > Andrey Repin (anrdae...@yandex.ru) 13.03.2014, <00:14> > > Sorry for my terrible english... > -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
