Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

When I use putty, login and type "screen", it works.

When I use a DIFFERENT computer--a linux based system. I SSH into it through my local machine. Then, I type "screen" , and it displays this error?:

'cannot open your terminal '/dev/pts/0' -please check
share|improve this question

migrated from stackoverflow.com Oct 21 '09 at 4:33

This question came from our site for professional and enthusiast programmers.

    
serverfault.com/questions/116775/… –  Nakilon Dec 11 '13 at 15:20
add comment

3 Answers

up vote 5 down vote accepted

You've probably su'd to a user different than one you logged in as. You must run screen as the same user which owns the terminal device, which is the user you logged in as.

If you need to run commands as another user, start your screen and do your "su" from inside it.

share|improve this answer
    
i get the same error message when i su to a non-privileged user (other than the one i logged in as) and try to run screen. –  quack quixote Oct 21 '09 at 11:33
    
@quack: Uh, yes...? You are not contributing any new information, here. What are you trying to say? –  Teddy Oct 21 '09 at 18:09
    
@Teddy: Yes, I did su to the user different than one logged in. If so, can I still use screen? –  Alex Oct 23 '09 at 11:16
    
@Alex: Not like that. But you can start your screen and do your "su" inside it. –  Teddy Oct 23 '09 at 13:31
    
@Teddy: just verifying your diagnosis, that's all. –  quack quixote Oct 23 '09 at 14:05
add comment

Are you trying to reattach the session that was started elsewhere? If so, and the other session hasn't dettached, you need to do screen -d -r <sessionname>.

If it's merely starting screen, then I'm not sure.

share|improve this answer
add comment

Is the machine on which you are having problems known to be particularly "locked down"?

It seems like it might be a permissions problem with your pseudo-terminal. After getting this error message, check the output of ls -l /dev/pts/0 (use the path from the error message). If it does not show you as the owner with read and write bits, then you may check it out with the machine's administrator.

I can imagine a system that would chown-away and chmod-down a pseudo-terminal after the initial login process gets going (sub-processes could inherit the already open file handles for std{in,out,err}), but that would be pretty draconian. What does mount | grep pts show? Maybe the mount options are setup incorrectly…

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.