DDraceNetwork - questions

why is this even possible

14:24

i’m hosting a server and you can use a vpn to connect more than once

there just is no vpn/ip Blocklist by default

14:41

you can set one up with dnsbl settings https://ddnet.org/settingscommands/

question about server hosting

15:45

i’m running it on a raspberry pi and when it’s running i no longer have access to the terminal. is there a way to keep the server running while also being able to use the terminal at the same time

screen

15:47

but tbh that is not a question for this channel. also a quick google would have told you^^

LuKron

i’m running it on a raspberry pi and when it’s running i no longer have access to the terminal. is there a way to keep the server running while also being able to use the terminal at the same time

will help anyway - you can launch it like this: ./DDNet-Server & which sends it to the background and makes it so you can still use the terminal terminating wont work using ctrl+c and it will keep on executing even if you close the terminal - if you want to terminate the process now you need to find the PID of the process and kill it: ps aux | grep DDNet look for the DDNet-Server process now kill <PID> (it might also work with pkill DDNet-Server but im not quite sure) it'll look something like this: melon 28097 0.0 0.0 4749172 21268 pts/2 Sl 17:48 0:00 ./DDNet-Server where 28097 is the <PID> (edited)

I would run it in screen or tmux tbh, if you just background it it will keep spewing into stdout messing up your terminal experience

Learath2

I would run it in screen or tmux tbh, if you just background it it will keep spewing into stdout messing up your terminal experience

its a headless raspberry pi and he already had startup struggles, i wouldnt recommend going into tmux :D

Tmux mentioned

15:54

Pog

i mean the docker file works now thanks to furo afaik(?) - which is much easier to have it running in the background XD

Learath2

I would run it in screen or tmux tbh, if you just background it it will keep spewing into stdout messing up your terminal experience

would either of these or melons suggestion work if i turn off the laptop i used to ssh into the pi?

See that's the issue with melon's suggestion, killing the terminal usually kills bg processes

15:57

after 2 decades of using linux I still have to think about how to properly detach a process

Learath2

See that's the issue with melon's suggestion, killing the terminal usually kills bg processes

he wont kill the bg process if he is connected over ssh even if he closes the remote connection ? been a long time since i last used ssh, and when i do i usually do everything in docker :D (edited)

meloƞ

he wont kill the bg process if he is connected over ssh even if he closes the remote connection ? been a long time since i last used ssh, and when i do i usually do everything in docker :D (edited)

He will kill it, because the shell owns the process, so it'll send a HUP to its children as it dies (edited)

15:58

you can use disown on bash or run the command with nohup

LuKron

would either of these or melons suggestion work if i turn off the laptop i used to ssh into the pi?

IIRC you could use VSC on your host machine and connect over ssh to your raspberry pi over there, you can use its terminal while also modifying files and open multiple instances (of your terminal) (edited)

yeah but would it work if my laptop turns off?

you can use disown on bash or run the command with nohup

you would use learath's suggestion for that ig (edited)

All of the suggestions work, they all require you to research a bit about how to do it though. For screen you can start a screen, run your command then detach (ctrl+a, d iirc). For melons suggestion you need to figure out how to correctly disown processes for whatever shell you are using (disown in bash and I don't remember any others)

Learath2

All of the suggestions work, they all require you to research a bit about how to do it though. For screen you can start a screen, run your command then detach (ctrl+a, d iirc). For melons suggestion you need to figure out how to correctly disown processes for whatever shell you are using (disown in bash and I don't remember any others)

i’ve just looked into nohup and it seems easy enough to run.

16:04

i’ll try that out

2

cheers guys nohup worked

2

meloƞ

will help anyway - you can launch it like this: ./DDNet-Server & which sends it to the background and makes it so you can still use the terminal terminating wont work using ctrl+c and it will keep on executing even if you close the terminal - if you want to terminate the process now you need to find the PID of the process and kill it: ps aux | grep DDNet look for the DDNet-Server process now kill <PID> (it might also work with pkill DDNet-Server but im not quite sure) it'll look something like this: melon 28097 0.0 0.0 4749172 21268 pts/2 Sl 17:48 0:00 ./DDNet-Server where 28097 is the <PID> (edited)

that's what I did when I last launched a server. And yeah, closing the remote connection did not kill my process. Not that I know why though.

If I have the configuration to take screenshots at the end of the game, where should I look for the image in the folder? Or should I configure something? In Linux, What is the path to get to the file (edited)

'Schwi♫

If I have the configuration to take screenshots at the end of the game, where should I look for the image in the folder? Or should I configure something? In Linux, What is the path to get to the file (edited)

appdata ddnet screenshots

Jupstar ✪

appdata ddnet screenshots

The folder does not appear

appdata teeworlds screenshots

$configdir

DDNet config directory & settings_ddnet.cfg location:

On Windows: Old: %appdata%\Teeworlds New: %appdata%\DDNet On Linux: Old: ~/.teeworlds New: ~/.local/share/ddnet On macOS: Old: ~/Library/Application Support/Teeworlds New: ~/Library/Application Support/DDNet The settings_ddnet.cfg file contains all your friends, control, player & game settings.