From: Juan Martin <nauj27@te...> - 2003-08-02 11:47:08
I have a sever mounted with Debian GNU/Linux and have some questions
about the remote control of core. All is shown perfectly from here, my
personal computer with gui but if core die or I want to kill it and
reload it I should to go phisicaly to the server.
This is because if I access by ssh the core die when I close the ssh
session and don't find option in the gui for launch it. It's possible to
launch the remote core in the away computer? (from ssh, gui... etc)
Juan Mart=EDn L=F3pez
Usuario Linux: 196702
M=E1quina Linux: 87473
Usuario de Debian GNU/Linux SID
Miembro de GCUBO.ORG (Grupo GNU Granadino)
Linux, because rebooting is for adding new hardware ...
> I have a sever mounted with Debian GNU/Linux and have some questions
> about the remote control of core. All is shown perfectly from here, my
> personal computer with gui but if core die or I want to kill it and
> reload it I should to go phisicaly to the server.
> This is because if I access by ssh the core die when I close the ssh
> session and don't find option in the gui for launch it. It's possible to
> launch the remote core in the away computer? (from ssh, gui... etc)
You should use the 'screen' utility to launch your core in a remote ssh
session, and then put the core into the background with Control-A, Control-D.
ie. like this:
screen -dmS overnet /home/juan/bin/on/overnet0.49.5 - !
screen -d -r overnet
The '-' makes the core listen for a GUI, and the '!' makes the core ingore all
keyboard input. Those are optional of course.
If you want to remote control that core via a GUI, you need to set up a GUI
username/password first with:
% cd /home/juan/bin/on/
> pass juan juanpass
Do you really want to quit? (y/n) yes
and then do the above with screen.
From: Thomas Ritter <th.ritter@gm...> - 2003-08-02 17:00:18
Am Samstag, 2. August 2003 15:29 schrieb Tim Müller:
> screen -dmS overnet /home/juan/bin/on/overnet0.49.5 - !
or if the donkey core is to be started anyway, you could make a service in
su -c "overnet0.49.5 - !" yourusername
There are always skeleton files in /etc/init.d to have a good starting point.
And don't start it as root, maybe even with an own user id and group inside a
chroot environment (should be fairly easy with overnet/donkey), just for the
case that there are security holes. Network services like the donkey are
always suspectible tio have holes ;)
Greetings from an xmule user missing the good old core/gui separation,
"Those who would give up essential liberty, to purchase a little temporary
safety, deserve neither liberty nor safety." - Benjamin Franklin