<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Screen on Debian Addict</title>
    <link>https://debianaddict.com/tags/screen/</link>
    <description>Recent content in Screen on Debian Addict</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Fri, 08 Mar 2013 10:47:46 +0000</lastBuildDate>
    <atom:link href="https://debianaddict.com/tags/screen/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>su&#43;screen: &#34;Cannot open your terminal &#39;/dev/pts/0&#39; - please check.&#34;</title>
      <link>https://debianaddict.com/2013/03/08/gnu-screen-cannot-open-terminal-when-you-su-to-a-user/</link>
      <pubDate>Fri, 08 Mar 2013 10:47:46 +0000</pubDate>
       <guid isPermaLink="false">http://debianaddict.com/?p=56</guid> 
      <description>&lt;p&gt;Quick tip this time.&lt;/p&gt;
&lt;p&gt;Often enough, one is logged in as root and decides to su - to an underprivileged user. Due to the tty for the root shell being owned by the user root, the su&amp;rsquo;d environment is unable to run screen:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;root@whitegirl:~# su - joe joe@whitegirl:~$ screen Cannot open your terminal &#39;/dev/pts/0&#39; - please check. joe@whitegirl:~$ &lt;/code&gt;&lt;/p&gt;
&lt;p&gt;This is resolved by setting the owner of the terminal device to the target user before running su, so the user then has write privileges on the pseudo teletype device:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
