I've always loved robotics so I focused on learning that. I've worked on destkop applications, on drones, and now on exoskeletons! Web dev looks scary to me but there is a lot of potential there.
Location
France
Education
Master of Engineering
Work
Critical Embedded Software engineer at Wandercraft
I've always loved robotics so I focused on learning that. I've worked on destkop applications, on drones, and now on exoskeletons! Web dev looks scary to me but there is a lot of potential there.
Location
France
Education
Master of Engineering
Work
Critical Embedded Software engineer at Wandercraft
I am a professional DevOps Engineer with a demonstrated history of working in the internet industry. I am an avid Linux lover and supporter of the open-source movement philosophy.
Location
Sofia, Bulgaria
Work
Developer Advocate at Materialize | Community Manager at DigitalOcean | Co-Founder at DevDojo
There is also the
nohup
commandJust be careful because by default it opens a nohup.out file and appends all output of the process you launched into this file. It can grow a lot.
If you're afraid of filling your disk, just toss the output to
/dev/null
during the command invocation ;)I highly recommend this command, we use this on daily basis instead of 3rd party tools.
Thanks for sharing Loik! I’ll definitely check it out!
If I may ask how do you handle killing the process?
This is my go-to
nohup command ... &