On Thu, Jul 17, 2008 at 7:02 PM, Samir Unni <
address@hidden> wrote:
> Hi,
>
> Whenever this happens to me, I just run 'screen -x <session name>' and wait
> for 10-15 minutes for it to successfully connect. The best thing to do would
> be to avoid sending too much data over a low bandwidth connection. I try to
> prevent this as often as possible, but sometimes I forget to filter the
> output or something. I don't know of any permanent solution.
>
> Thanks,
>
> Samir Unni
>
>
> On Wed, Jul 16, 2008 at 8:29 AM, Pandurangan R S <
address@hidden>
> wrote:
>>
>> Hi,
>>
>> My screen looks to be frozen. screen -x (or screen -d) also gets stuck.
>>
>> I recently saw a thread which talks about accidentally locking the
>> screen and thinking it is frozen.
>> Is the case with my screen now? If so, how can i unlock it?
>>
>>
>> If I strace the screen process, I observe the following. Any hints?
>>
>> Process 15342 attached - interrupt to quit
>> pause() = ? ERESTARTNOHAND (To be
>> restarted)
>> --- SIGALRM (Alarm clock) @ 0 (0) ---
>> sigreturn() = ? (mask now [])
>> alarm(0) = 0
>> kill(6866, SIG_0) = 0
>> rt_sigaction(SIGALRM, {0x806a540, [], 0}, {0x806a540, [], 0}, 8) = 0
>> alarm(15) = 0
>> pause() = ? ERESTARTNOHAND (To be
>> restarted)
>> --- SIGALRM (Alarm clock) @ 0 (0) ---
>> sigreturn() = ? (mask now [])
>> alarm(0) = 0
>> kill(6866, SIG_0) = 0
>> rt_sigaction(SIGALRM, {0x806a540, [], 0}, {0x806a540, [], 0}, 8) = 0
>> alarm(15) = 0
>> pause(
>>
>> Thanks
>> Pandu
>>
>>
>> _______________________________________________
>> screen-users mailing list
>>
address@hidden
>>
http://lists.gnu.org/mailman/listinfo/screen-users
>
>