My best guess here is:
- @testteam is trying to run
screen command and getting
screen complaining about not being able to open terminal.
- In the answer linked, solution mentioned is to use
script /dev/null and that should resolve the issue.
- @testteam is wondering if that's going to affect any servers running on the machine (probably in the
This answer has very good explanation what
script command is going to do and why
screen is complaining:
Why this works is invoking
script has a side effect of creating a pseudo-terminal for you at
/dev/pts/X. This way you don't have to do it yourself, and
screen won't have permission issues - if you
su from user A to user B, by directly invoking screen you try to grab possession of user A's pseudo-terminal. This won't succeed unless you're root.
So the fact that
script solves the issue with
screen is basically side effect. I'm guessing that you want to run some node.js app in the
screen session. The fact that you created
pts device and used
script for that should not affect servers or (web)apps running inside screen session.