This is the mail archive of the
mailing list for the Cygwin project.
Re: screen-4.0.2 on Cygwin 1.5.R18-1
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Peter <pli9+PUB at borkborkbork dot itsa dot ucsf dot edu>
- Cc: cygwin at cygwin dot com
- Date: Fri, 2 Dec 2005 10:21:35 -0500 (EST)
- Subject: Re: screen-4.0.2 on Cygwin 1.5.R18-1
- References: <firstname.lastname@example.org> <Pine.LNX.email@example.com>
- Reply-to: cygwin at cygwin dot com
On Fri, 2 Dec 2005, Peter wrote:
> I got screen to compile with very minor source code changes (more
> changes might be better, but I haven't fiddled too much). Everything
> seems to work okay, except that I can't get screen to persist once I
> close my terminal window.
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...
> I tried running screen "-d -m" as a service through cygrunsrv, but with
> little success. When it runs as SYSTEM I can't attach the screen, and
> when it runs as me it hangs immediately. It seems to hang eventually
> when running as SYSTEM too, but it's hard to tell what's going on.
> Anyone who can tell me a better way?
What is the error message when screen runs as SYSTEM? I suspect it's a
fifo permission issue...
As for hanging does it consume CPU at all? Try attaching to the process
with strace and seeing where it hangs.
If you wish for others to try reproducing your behavior, please post the
"minor changes" you mentioned above (as a patch).
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html