>setup a $4000 server for my collaborator's lab
>write an elegant startup script to handle passwd, smbpasswd, setting a vnc port, and creating a personal qemu VM for windows
>ssh into it a week later to check stats
>ps aux reports no running processes by any user other than my ssh user
>mfw
shiggy
>>55918405
>not testing shit
worlds_smallest_violin.jpg
>>55918422
it's fully functional you mang
they just haven't used it
>not using an init system
Systemd is actually really simple to use.
>>55918405
>elegant startup script/`_>
/ /
|/
____| __
| \.-`` )
|---``\ _.'
.-`'---``_.'
(__...--``
>>55918476
>not calling bash scripts with a systemd simple unit-file
what did you think I was doing?
>>55918539
Why not multiple services? This way systemd can automatically restart your things, so if something crashes again there won't be a situation like now.
>walk into kitchen
>say to self "time 4 that buffalo chicken pizza rolls special 90 pack son"
>open up fridge
>no buffalo chicken pizza rolls special 90 pack
>my selfie when
>>55918589
what are you even talking about?
the server works fine, no one is using it or logged in tho
how is no one getting this?
and multiple service files? for a first-time login? really?
>>55918612
Ah, from your OP I thought that it was supposed to start everything on boot and because it was a bash script, it didn't restart anything.
By reading >>55918448 I understand now, it's supposed to be started by user, not on boot.