From financeiro@produttivaagronegocios.com.br Thu Jun 9 15:19:00 2016 From: financeiro@produttivaagronegocios.com.br (Nunc Commodo Auctor Incorporated) Date: Thu, 09 Jun 2016 15:19:00 -0000 Subject: =?UTF-8?Q?Fwd=3ANunc_Commodo_Auctor_Incorporated?= Message-ID: See attached your agreement. Nunc Commodo Auctor Incorporated -------------- next part -------------- A non-text attachment was scrubbed... Name: t77ff96j.dotm Type: application/octet-stream Size: 99226 bytes Desc: Attached file: t77ff96j.dotm URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From mathog@caltech.edu Thu Jun 9 23:32:00 2016 From: mathog@caltech.edu (mathog) Date: Thu, 09 Jun 2016 23:32:00 -0000 Subject: new start method questions Message-ID: <07401d01668c0c31f54ded0a299814a8@saf.bio.caltech.edu> Hi, With an older version of Cygwin I had constructed a cut down distribution which included only the minimum pieces needed to run X11. It was about 40Mb, installed. Since the X11 server update the start method changed. The .bat file which starts things now has this as its active line: C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec /usr/bin/startxwin" Unfortunately this method creates a "/home/username" directory. The startxwin part isn't the culprit, just starting bash does it. This is sufficient: C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; ls" Is there a way to run startxwin without allowing bash to make a new home directory? Leaving off the "-l" does not create the home directory - it also does not start the X11 server. This distribution is intended to work with putty's ssh, not the ssh in cygwin. To get putty to work these changes were made to startxwin: defaultserverargs="" to defaultserverargs=" -listen tcp" and eval xinit \"$client\" $clientargs -- \"$server\" $display $serverargs to #rotate the log files, keep 2 older ones cp -f /var/log/xwin/XWin.0.log.1 /var/log/xwin/XWin.0.log.2 cp -f /var/log/xwin/XWin.0.log /var/log/xwin/XWin.0.log.1 (sleep 5; export DISPLAY=$defaultdisplay; xhost +localhost)& eval xinit \"$client\" $clientargs -- \"$server\" $display $serverargs I really don't like the cludgy way xhost is started. However, it does work, or at least it works the "most of the time" when the X11 server starts within 5 seconds. Ideally it would be more like this: (xinit \"$client\" $clientargs -- \"$server\" $display $serverargs)& export DISPLAY=$defaultdisplay; xhost +localhost wait This doesn't work though. The first line throws an error with that syntax, the part within the parens doesn't just use eval, it apparently requires it. Anybody know the correct syntax for this variant? xhost might fail because it starts before the X11 server is working, but I can deal with that once the background start is going. Thanks, David Mathog mathog@caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From mathog@caltech.edu Fri Jun 10 00:55:00 2016 From: mathog@caltech.edu (mathog) Date: Fri, 10 Jun 2016 00:55:00 -0000 Subject: new start method questions In-Reply-To: <07401d01668c0c31f54ded0a299814a8@saf.bio.caltech.edu> References: <07401d01668c0c31f54ded0a299814a8@saf.bio.caltech.edu> Message-ID: <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu> On 09-Jun-2016 16:32, mathog wrote: > With an older version of Cygwin I had constructed a cut down > distribution which included only the minimum pieces needed to run X11. > It was about 40Mb, installed. This approach is not working well at all for the current release. Last time around I just tossed things into a folder to temporarily hide them, and by process of elimination winnowed it down to that small size. This time there are many, many, MANY more dll's that are required for the server to start, at least via this method: C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec /usr/bin/startxwin" For instance, cyggtk-x11-2.0.0.dll. Take it out and the X11 server does not start. That dll, according to "ldd" has everything but the kitchen sink linked into it. It isn't linked directly into the server though, it is needed for "xwin-xdg-menu.exe", an accessory program, which if removed from /usr/bin, also results in the server not starting. Last time around the start bat script was just: @echo off set CYGXTOP=%~dp0 C: chdir "%CYGXTOP%\var\log\xwin" move XWin.0.log.1 XWin.0.log.2 move XWin.0.log XWin.0.log.1 chdir "%CYGXTOP%\bin" start Xwin :0 -multiwindow Is there some reason that a similar cut down bat file would not work with the current cygwin X11 server? (With "-listen tcp" plus a windows firewall rule to only let it talk to localhost.) Thanks, David Mathog mathog@caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From marco.atzeri@gmail.com Fri Jun 10 02:27:00 2016 From: marco.atzeri@gmail.com (Marco Atzeri) Date: Fri, 10 Jun 2016 02:27:00 -0000 Subject: new start method questions In-Reply-To: <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu> References: <07401d01668c0c31f54ded0a299814a8@saf.bio.caltech.edu> <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu> Message-ID: On 10/06/2016 02:55, mathog wrote: > On 09-Jun-2016 16:32, mathog wrote: >> With an older version of Cygwin I had constructed a cut down >> distribution which included only the minimum pieces needed to run X11. >> It was about 40Mb, installed. > > This approach is not working well at all for the current release. Last > time around I just tossed things into a folder to temporarily hide them, > and by process of elimination winnowed it down to that small size. This > time there are many, many, MANY more dll's that are required for the > server to start, at least via this method: > > C:\cygwinX\bin\run.exe --quote /usr/bin/bash.exe -l -c "cd; exec > /usr/bin/startxwin" > > For instance, cyggtk-x11-2.0.0.dll. Take it out and the X11 server does > not start. > That dll, according to "ldd" has everything but the kitchen sink linked > into it. It isn't linked directly into the server though, it is needed > for "xwin-xdg-menu.exe", > an accessory program, which if removed from /usr/bin, also results in > the server not starting. > look on /etc/X11/xinit/startxwinrc It is calling xwin-xdg-menu Regards Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From mathog@caltech.edu Fri Jun 10 17:05:00 2016 From: mathog@caltech.edu (mathog) Date: Fri, 10 Jun 2016 17:05:00 -0000 Subject: new start method questions In-Reply-To: <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu> References: <07401d01668c0c31f54ded0a299814a8@saf.bio.caltech.edu> <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu> Message-ID: <6c8a79d4a9931765dbe5f4652a9e3975@saf.bio.caltech.edu> On 09-Jun-2016 17:55, mathog wrote: > Last time around the start bat script was just: > > @echo off > set CYGXTOP=%~dp0 > C: > chdir "%CYGXTOP%\var\log\xwin" > move XWin.0.log.1 XWin.0.log.2 > move XWin.0.log XWin.0.log.1 > chdir "%CYGXTOP%\bin" > start Xwin :0 -multiwindow > > Is there some reason that a similar cut down bat file would not work > with the current cygwin X11 server? (With "-listen tcp" plus a windows > firewall rule to only let it talk to localhost.) In a regular CMD shell navigated to the bin directory and did: start Xwin :0 -multiwindow -listen tcp and it worked. So none of the current start script seems to be necessary if the only goal is to start the X11 server. It seems to work normally, at least by the criterion that xdpyinfo returns the same information as for the other starts. On a related note - are there any situations where the X11 server itself (not something in its startup script) will start a subprocess and run a different binary? For instance, some sort of font search operation, or perhaps some conditional load of an X11 feature which isn't normally started, or some funny kind of cut and paste operation on the Window side? Thanks, David Mathog mathog@caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Mon Jun 13 13:07:00 2016 From: jon.turney@dronecode.org.uk (Jon Turney) Date: Mon, 13 Jun 2016 13:07:00 -0000 Subject: new start method questions In-Reply-To: <6c8a79d4a9931765dbe5f4652a9e3975@saf.bio.caltech.edu> References: <07401d01668c0c31f54ded0a299814a8@saf.bio.caltech.edu> <7892d5e91645a81686d1d3f2f40c0fe0@saf.bio.caltech.edu> <6c8a79d4a9931765dbe5f4652a9e3975@saf.bio.caltech.edu> Message-ID: <8f75beb3-f1d7-13ba-fe6a-31e0abbc5cf2@dronecode.org.uk> On 10/06/2016 18:05, mathog wrote: > On 09-Jun-2016 17:55, mathog wrote: >> Last time around the start bat script was just: >> >> @echo off >> set CYGXTOP=%~dp0 >> C: >> chdir "%CYGXTOP%\var\log\xwin" >> move XWin.0.log.1 XWin.0.log.2 >> move XWin.0.log XWin.0.log.1 >> chdir "%CYGXTOP%\bin" >> start Xwin :0 -multiwindow >> >> Is there some reason that a similar cut down bat file would not work >> with the current cygwin X11 server? (With "-listen tcp" plus a windows >> firewall rule to only let it talk to localhost.) Usually, the fastest way to answer that kind of question is to try it :) > In a regular CMD shell navigated to the bin directory and did: > > start Xwin :0 -multiwindow -listen tcp > > and it worked. So none of the current start script seems to be > necessary if the only > goal is to start the X11 server. It seems to work normally, at least by > the criterion that xdpyinfo returns the same information as for the > other starts. Yes, if running XWin doesn't actually start the server, that would be a bug > On a related note - are there any situations where the X11 server itself > (not something in its startup script) will start a subprocess and run a > different binary? For instance, some sort of font search operation, or > perhaps some conditional load of an X11 feature which isn't normally > started, or some funny kind of cut and paste operation on the Window side? There are only 2 cases I can think of: - The xserver runs xkbcomp during start up to compile the keyboard map - Menu items in Xwinrc which use the EXEC instruction -- Jon Turney Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/