Timeline for Running process in background ruins terminal
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 12, 2022 at 9:12 | comment | added | hudac |
I want them to not get ruined at all. I'm not sure what's the point of this process I start, that it messing with the terminal. I edited my question - I wrote that when I start this process with sudo it happens. But if I start it without sudo it does not happen
|
|
| Sep 12, 2022 at 9:07 | comment | added | Andre Beaud | exactly - try typing it when you need things to be back to normal again | |
| Sep 12, 2022 at 7:06 | comment | added | hudac |
Thanks for the answer: I've already tried < /dev/null - it didn't work. It is a daemon that get started using systemd. But I currently start it in development environment inside a docker container where I don't have systemd, so I need to start it manually. stty sane - should I run it afterwards, like reset?
|
|
| Sep 12, 2022 at 3:59 | history | answered | Andre Beaud | CC BY-SA 4.0 |