X-Spam-Check-By: sourceware.org Date: Fri, 2 Dec 2005 15:46:16 -0500 (EST) From: Peter To: cygwin AT cygwin DOT com, Igor Pechtchanski Subject: Re: screen-4.0.2 on Cygwin 1.5.R18-1 In-Reply-To: Message-ID: References: <1133503614 DOT 349 DOT ezmlm AT cygwin DOT com> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-141759415-74247323-1133556307=:31904" Content-ID: Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com ---141759415-74247323-1133556307=:31904 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: Thanks for your quick reply. It gives me a bit more to think about; I don't really know my way around cygwin/*nux that well, from the administrative end; I've just been an end user for a long time. > How exactly do you invoke screen? Does "setsid" work for you? Does > "nohup"? IIRC, bash also has an option for controlling whether background > processes are terminated on exit... How will I know whether setsid is working? I tried setting the setuid bits via chmod, but I don't know what I'm doing other than that. I'll try nohup and look through the shell documentation for options. I'm either invoking screen from the command line as my user, or as SYSTEM (by scheduling a cmd window with the NT "at" command). This works okay, but the process does not persist. I've tried running it as a service like so: cygrunsrv -I screen -p /usr/local/bin/screen -a '-d -m' cygrunsrv -S screen I get the hanging, plus it runs as SYSTEM unless I add the options to run it as myself. Now that I think of it, perhaps I need to add -i for interactive; I'll try that. > What is the error message when screen runs as SYSTEM? I suspect it's a > fifo permission issue... I haven't figured out how to get the error messages out of cygrunsrv processes, but I should be able to figure that out and get back to you. I know that it runs okay up to a point as SYSTEM because it creates a new S-SYSTEM directory in /tmp/uscreens and creates fifos there (which I can investigate post hoc by taking control of the directory). > As for hanging does it consume CPU at all? Try attaching to the process > with strace and seeing where it hangs. Will do. > If you wish for others to try reproducing your behavior, please post the > "minor changes" you mentioned above (as a patch). Here you go. Like I said: very minor changes. More intelligent changes are almost certainly possible, but I don't really have time to read through the source code and figure things out much more. Have other people done more meticulous patching? Most patches I googled are now 404. Thanks! P ---141759415-74247323-1133556307=:31904 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=screen-4.0.2-cyg.diff Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME=screen-4.0.2-cyg.diff ZGlmZiAtciBzY3JlZW4tNC4wLjIvbWlzYy5jIHNjcmVlbi00LjAuMi1jeWcv bWlzYy5jDQo2MTVhNjE2DQo+ICMgZGVmaW5lIGxpbnV4DQo2MjBhNjIyDQo+ ICMgdW5kZWYgbGludXgNCmRpZmYgLXIgc2NyZWVuLTQuMC4yL3B0eS5jIHNj cmVlbi00LjAuMi1jeWcvcHR5LmMNCjM4YzM4DQo8ICMgaW5jbHVkZSA8c3lz L3N0cm9wdHMuaD4NCi0tLQ0KPiAvKiAjIGluY2x1ZGUgPHN5cy9zdHJvcHRz Lmg+ICovDQpkaWZmIC1yIHNjcmVlbi00LjAuMi91dG1wLmMgc2NyZWVuLTQu MC4yLWN5Zy91dG1wLmMNCjU5MWE1OTINCj4gI2RlZmluZSBsaW51eA0KNTk4 YTYwMA0KPiAjdW5kZWYgbGludXgNCg== ---141759415-74247323-1133556307=:31904 Content-Type: text/plain; charset=us-ascii -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ ---141759415-74247323-1133556307=:31904--