have to get used to having 1 less terminal window open all the time ever since shutting down the snake bot

edit: i have notifications muted on this thread, i might not see your replies

i keep pressing super+5 to get to firefox, but now it is super+4

@kemona_halftau you kept it in an open terminal window?

@luana uhhm how else would i have run it

@luana /genq

@kemona_halftau @luana systemd unit?

@kemona_halftau @luana or maybe docker (derogatory)

@solonovamax @luana idk i just like having a bunch of terminal windows always open on my second monitor, its pleasant to look at imo (and also i can very quickly and immediately restart things if/when i need to)

@solonovamax @luana @kemona_halftau the simpler way i would say is you can always ./program &; disown $pid which forks it and disowns it

@pastthepixels @solonovamax @luana is that similar to nohup?

@kemona_halftau @luana tmux/screen/dtach or init system (user) service or just running in the background with & (or ^Z and bg) and disowning the process

@kemona_halftau @luana I already have so many terminals it starts to get messy

also, restarting is super easy

# systemctl restart program

@solonovamax @luana vs ^c, up arrow, enter?

@kemona_halftau @solonovamax it has autorestart on crashes and stuff

@kemona_halftau As a systemd service!!

With autostart, autorestart and stuff

(Or openrcs equivalent, if that's what your distro uses)

@kemona_halftau i forgot what that is, one sec

@kemona_halftau no it still gets killed when you log out

@kemona_halftau ok the more i read this the more i'm confused, because my operating systems class taught me that a parent process forking a child process still owns the child, and if the parent is killed so is the child, but you have to call some system call to disown the process and make it Not do that... but idk my memories are kind of a garble

@kemona_halftau @luana

sudo sy[tab] re[tab] pr[up arrow or tab]

@kemona_halftau @pastthepixels @luana this summarizes the differences: https://unix.stackexchange.com/questions/3886/difference-between-nohup-disown-and

@solonovamax @kemona_halftau @luana there’s too many commands beginning with sy (even installed by systemd, there’s a load of systemd-*) and systemctl subcommands beginning with re for that to work. on my server the shortest unique tab completion is sudo systemc[tab] rest[tab]

@pastthepixels @kemona_halftau testing using this program:

#include <stdio.h>
#include <unistd.h>

int main(void) {
        pid_t pid = fork();
        switch (pid) {
        case -1:
                perror("fork");
                return 1;
        case 0: // child
                printf("child\n");
                for (;;) pause();
        default: // parent
                printf("parent, child PID = %d\n", pid);
                return 0;
        }
}

the child process does not get killed when the parent terminates. on linux, you can set the signal child processes receive when the parent dies using prctl(PR_SET_PDEATHSIG, …), but by default the child processes do not get killed when the parent dies

@noisytoot @kemona_halftau @luana oh right

I was typing that on my phone

still, typing it out doesn't that that long

@solonovamax @noisytoot @kemona_halftau if you have a particularly problematic serviço it'll always be the first autocomplete from sys anyway

@luana @noisytoot @kemona_halftau the humble systemd timer to restart a systemd unit every n hours: