On Wed 03 Nov 04, 10:56 AM, ME <[EMAIL PROTECTED]> said:
If you have never used the share option before, it allows two people
to
"share" a screen session; both people may type in the same session at
the
same time and have the same privs as shell in the given session. You
are
able to specify what
On Wed 03 Nov 04, 10:56 AM, ME <[EMAIL PROTECTED]> said:
> Karsten M. Self said:
> > on Mon, Nov 01, 2004 at 09:07:21AM -0800, Ken Bloom ([EMAIL PROTECTED])
> > wrote:
> >> On Mon, 1 Nov 2004 11:53:30 -0500
> >> [EMAIL PROTECTED] (Peter Jay Salzman) wrote:
> >
> > ['screen' reattaching not working]
Karsten M. Self said:
> on Mon, Nov 01, 2004 at 09:07:21AM -0800, Ken Bloom ([EMAIL PROTECTED])
> wrote:
>> On Mon, 1 Nov 2004 11:53:30 -0500
>> [EMAIL PROTECTED] (Peter Jay Salzman) wrote:
>
> ['screen' reattaching not working]
>
>> See if you can work around the problem by using
>> $ screen -d -R
on Mon, Nov 01, 2004 at 09:07:21AM -0800, Ken Bloom ([EMAIL PROTECTED]) wrote:
> On Mon, 1 Nov 2004 11:53:30 -0500
> [EMAIL PROTECTED] (Peter Jay Salzman) wrote:
['screen' reattaching not working]
> See if you can work around the problem by using
> $ screen -d -R
> (both parameters at the same t
On Mon, 1 Nov 2004 12:26:01 -0500
[EMAIL PROTECTED] (Peter Jay Salzman) wrote:
> On Mon 01 Nov 04, 9:07 AM, Ken Bloom <[EMAIL PROTECTED]> said:
> > On Mon, 1 Nov 2004 11:53:30 -0500
> > [EMAIL PROTECTED] (Peter Jay Salzman) wrote:
> >
> > > Thanks Mike. I did try the remote detach (-d). It *sa
On Mon 01 Nov 04, 9:07 AM, Ken Bloom <[EMAIL PROTECTED]> said:
> On Mon, 1 Nov 2004 11:53:30 -0500
> [EMAIL PROTECTED] (Peter Jay Salzman) wrote:
>
> > Thanks Mike. I did try the remote detach (-d). It *said* that the
> > session was forcibly detached, but a subsequent "screen -ls" showed
> > t
On Mon, 1 Nov 2004 11:53:30 -0500
[EMAIL PROTECTED] (Peter Jay Salzman) wrote:
> Thanks Mike. I did try the remote detach (-d). It *said* that the
> session was forcibly detached, but a subsequent "screen -ls" showed
> the session as still being attached.
>
> Here's an example:
>
>
># Try
Thanks Mike. I did try the remote detach (-d). It *said* that the session
was forcibly detached, but a subsequent "screen -ls" showed the session as
still being attached.
Here's an example:
# Try to reattach
#
born$ screen -r
There is a screen on:
25783.pts-2.born
Peter Jay Salzman said:
> There's a bunch of computers that have NFS mounted /home.
[chop]
> The screen sessions are saved in $HOME/.screen. Typical socket:
>
>kusch$ ls -la .screen/
>total 8.0K
>drwx--2 psalzman g96 4.0K Oct 31 20:36 ./
>drwx-- 32 psalzman g
If a session is still attached according to the system, you can try to
issue a remote detatch:
(new shell, login from a non-screen session on the box)
$ screen -d
Another option is to try a force re-attach with "-R" (includes existing
attached sessions as wells as ones which are detatched.)
$ scre
There's a bunch of computers that have NFS mounted /home. I log into these
computers to run simulations. In the past, I've used screen to leave a job
running and come back to it a few days later to check up on the output.
The screen sessions are saved in $HOME/.screen. Typical socket:
kusch
11 matches
Mail list logo
