[bf1942] nice'ing processes

[+Mc+ FragMeister]

I think that's going to have to be patched. :)

-----Original Message-----
From: Robert Cash [mailto:rbcash at covad.net]
Sent: Tuesday, February 04, 2003 3:24 PM
To: bf1942 at icculus.org
Subject: RE: [bf1942] nice'ing processes


Dice needs to apply the following query:
SELECT * FROM Corporate_Drones WHERE clue > 0

-----Original Message-----
From: Bill Wood [mailto:wawoodtx at attbi.com]
Sent: Tuesday, February 04, 2003 1:47 PM
To: bf1942 at icculus.org
Subject: RE: [bf1942] nice'ing processes


Screen -D -R pid.tty works, too.

-----Original Message-----
From: Daniel E. Atencio Psille [mailto:dea at atencio.de]
Sent: Tuesday, February 04, 2003 1:23 PM
To: bf1942 at icculus.org
Subject: AW: [bf1942] nice'ing processes


about using screen:

'screen -ls' produces some output similar to this one:

dea at p15102942:~$ screen -ls
There is a screen on:
        2610.pts-2.p15102942    (Detached)
1 Socket in /var/run/screen/S-dea.

Watch '(Detached)' !! I haven't tried it yet, but I guess this might be
your problem. Maybe the use of screen in your startup script doesn't
leave the screen session detached but instead attached. If so, you could
use 'screen -d <sessionname>' or if this doesn't work 'screen -D
<sessionname>' to detach the session where '<sessionname>' is the
complete session-id (here: 2610.pts-2.p15102942). After that either call
of 'screen -r <sessionname>' or <screen -R <sessionname>' should work.

If all this won't do, you could try 'screen -D <sessionname>' to force
detaching of the session and 'screen -r <sessionname>' afterwards.

If I might suggest to rtfm in the future - starting apps under different
user contexts: man sudo || man su && http://tldp.org/docs.html#HOWTO

Daniel

> -----Ursprüngliche Nachricht-----
> Von: zextra at neobee.net [mailto:zextra at neobee.net]
> Gesendet: Dienstag, 4. Februar 2003 10:20
> An: bf1942 at icculus.org
> Betreff: Re: [bf1942] nice'ing processes
>
>
[ ... snip ... ]

> about screens under root... let me explain it a bit more... i
> write some script
> that contain only 1 command (eg. "screen -d -m -S
> some_sess /usr/blahblah/app"), and in rc.sysinit, at the end
> of all, i put call
> for this script to execute. AND, the system boots up, i login
> as root, type in
> screen -list, and i get NOTHING.... :( but, the command "ls
> /tmp/screens/S- root" shows me that there is some screen
> session named eg. 34523.some_sess. the
> question is: how can i attach on that session.

[ ... snap ...]