On Dec 20 Paul Everlund wrote:
> On Fri, 20 Dec 2002, Paul Everlund wrote:
>
> Found an error in my reply...
>
> > On Fri, 20 Dec 2002, Aaron Burke wrote:
> >
> [big snip]
>
> > I think execlp is writing over your current process. So first your
> > process is exchanged with ppp, then ppp is exchan
On Fri, 20 Dec 2002, Paul Everlund wrote:
Found an error in my reply...
> On Fri, 20 Dec 2002, Aaron Burke wrote:
>
[big snip]
> I think execlp is writing over your current process. So first your
> process is exchanged with ppp, then ppp is exchanged with screen. You
> have to make a copy of you
On Fri, 20 Dec 2002, Aaron Burke wrote:
> > 3. Avoid using system() which I vaguely recall being described with a
> >lot of bad words in various places and use fork(), exec(), _exit(),
> >waitpid() and exit() instead.
>
> How would I do this with exec. According to the man page for exec
>
> You're not running the executable as `root'. Since you are not the
> superuser, you do not have permissions to operate on the pseudo-tty
> that login attempts to work with, and this is why you get the
> following error message:
This is as I expected. And I dont know of a way to get around
it.
On 2002-12-19 02:50, Aaron Burke <[EMAIL PROTECTED]> wrote:
> I have an application that simply logs in as another user and runs
> "screen -x". The problem I am having with the followin code is that
> the results of execution is a message from (I am guessing the shell)
> saying that I dont have acc
Hello list
I have an application that simply logs in as another user
and runs "screen -x". The problem I am having with the
followin code is that the results of execution is a message
from (I am guessing the shell) saying that I dont have access
to the "/dev/ttyp?" where ? is the current virtual t
