Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 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? Commented Sep 12, 2022 at 7:06
  • exactly - try typing it when you need things to be back to normal again Commented Sep 12, 2022 at 9:07
  • 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 Commented Sep 12, 2022 at 9:12