On Sun, 17 Jun 2001, Shlomi Fish wrote:
> > (gdb) print open("/dev/tty4", 0) /* '0' stands for O_RDONLY */
> > $ = 4
> > (gdb) print dup2(4, 0);
> > $ = 0
> > (gdb) print open("/dev/tty4", 01) /* '01' stands for O_WRONLY */
> > $ = 5
> > (gdb) print dup2(5, 1);
> > $ = 0
> > (g
On Sun, 17 Jun 2001, Nadav Har'El wrote:
> On Sun, Jun 17, 2001, guy keren wrote about "Re: Background process I\O redirection":
> >...
> > 3. on a shell attached to '/dev/tty5' i run a debugger:
> > gdb /usr/bin/ncftp 7787
> >
> >
On Sun, 17 Jun 2001, guy keren wrote:
>
> in continuation to the previous post, i made a test that seemed to work
> (at least partially) to regain control of 'ncftp':
>
> 1. in a shell attached to /dev/tty1, i ran 'nohup ncftp'.
>i didn't connect to any server, and then ctrl-Z, 'bg', and 'exi
On Sun, Jun 17, 2001, guy keren wrote about "Re: Background process I\O redirection":
>
>...
> 3. on a shell attached to '/dev/tty5' i run a debugger:
> gdb /usr/bin/ncftp 7787
>
>in the debugger:
>
>(gdb) print open("/dev/tty4&q
in continuation to the previous post, i made a test that seemed to work
(at least partially) to regain control of 'ncftp':
1. in a shell attached to /dev/tty1, i ran 'nohup ncftp'.
i didn't connect to any server, and then ctrl-Z, 'bg', and 'exit' (had
to 'exit' twice, since the shell notic
On Sun, 17 Jun 2001 [EMAIL PROTECTED] wrote:
> Lets say I run something from a shell and detach it
> ($ ./some-proggie &)
> My question is whether Ican have any control of it's output\input after
> killing the shell itself. Some people I asked recommended a program named
> "screen", but frankly
Hello all.
This may sound like a newbie question, but I had no alternative but to
turn to the experts as no one on irc could answer it clearly :P
Lets say I run something from a shell and detach it
($ ./some-proggie &)
My question is whether I can have any control of it's output\input after
kil
